Repository navigation
fix: patch React Router 6 redirect handling - #193
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
7 tasks done
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.
Closes #192
Outcome
Patch the compatible React Router 6 graph that contains three high-severity audit findings, enable the two declarative-router compatibility flags deliberately, and preserve the club's route/callback behavior without a route redesign.
Reviewed source: 312be3b
Base main: efe82e1
Security boundary
Changes
Audit evidence
Node 20 production audit before:
Node 20 production audit after:
The package-lock identity diff contains exactly the three router package nodes.
Verification
Migration and rollback
No data migration. Roll back the package declaration, all three lock records, router flags, tests, and status documentation together if an exact deployment reveals a compatibility regression. Do not partially downgrade one router package.
Officer impact: None — the public route inventory and officer procedures do not change.
Officer documentation: None — dependency and tested router-compatibility patch only.
Deployment evidence: Source and local tests only at PR creation. No website publication, runmprc.com verification, Firebase deployment, Stripe/provider configuration, branch-setting change, or live behavior has occurred. Hosted PR and post-merge evidence will be recorded separately.