Repository navigation
Consolidate reviewed React and web toolchain upgrades - #36
Merged
Merged
Conversation
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The separate React and ReactDOM upgrade PRs produced mixed React 18/19 runtimes. Upgrade the pair and their types together, deduplicate the workspace, and migrate Vite, the React plugin and jsdom as one compatible group.
Preserve a space between navigation labels and counters for accessible names. Allow only the React 19 HTTPS diagnostic
/errors/URL family in the existing static egress scanner, with regressions that continue blocking non-diagnostic paths, lookalike hosts, HTTP and alternate ports. Rebuild the web assets packaged with the Python app.Validation: 562 Python tests and 67 UI tests passed; four egress scanner tests, production build, packaged-bundle synchronization, Ruff/evaluation checks, pip audit and npm production audit passed. Both browser E2E tests passed. CI passed on the exact PR head after aligning both workflows and documented requirements to Node 22.22.2, the minimum supported Node 22 release for jsdom 30.1.2. This consolidates the intent of dependency PRs #14–#18; no release publication is included.