Skip to content

[Snyk] Security upgrade react-router from 7.14.2 to 7.15.0 #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kagan-agent wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade react-router from 7.14.2 to 7.15.0 #168

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
"react-dom": "^19.2.5",
"react-hook-form": "^7.72.1",
"react-resizable-panels": "^4.10.0",
"react-router": "^7.14.1",
"react-router": "^7.15.0",

@greptile-apps greptile-apps Bot Jun 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Lockfile still pins old router The manifest now asks for react-router ^7.15.0, but the tracked pnpm-lock.yaml was not updated and still resolves the web package to react-router 7.14.2. With frozen pnpm installs, this can fail because the manifest and lockfile disagree; without a frozen install, the deployed dependency still comes from an uncommitted lockfile update, so this PR does not reliably apply the security upgrade.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: packages/web/package.json
Line: 39

Comment:
**Lockfile still pins old router** The manifest now asks for `react-router` `^7.15.0`, but the tracked `pnpm-lock.yaml` was not updated and still resolves the web package to `react-router` `7.14.2`. With frozen pnpm installs, this can fail because the manifest and lockfile disagree; without a frozen install, the deployed dependency still comes from an uncommitted lockfile update, so this PR does not reliably apply the security upgrade.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Claude Code Fix in Codex

"recharts": "^3.8.1",
"sonner": "^2.0.3",
"tailwind-merge": "^3.3.0",
Expand Down
Loading