[Snyk] Security upgrade next from 12.3.7 to 16.1.7#498
Conversation
…abilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NEXT-15674556 - https://snyk.io/vuln/SNYK-JS-NEXT-15674558
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3746821bd9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "jest": "^27.4.7", | ||
| "js-cookie": "^3.0.1", | ||
| "next": "^12.1.0", | ||
| "next": "^16.1.7", |
There was a problem hiding this comment.
Upgrading next to ^16.1.7 while leaving react/react-dom at ^17.0.2 creates an incompatible dependency set for this example, so installs/builds can fail or behave unpredictably depending on package-manager peer enforcement. In this same package.json, React is still pinned to 17 (lines 55-56), so this Next.js major bump should be paired with a React upgrade (and related package updates) rather than changed in isolation.
Useful? React with 👍 / 👎.
| "jest": "^27.4.7", | ||
| "js-cookie": "^3.0.1", | ||
| "next": "^12.1.0", | ||
| "next": "^16.1.7", |
There was a problem hiding this comment.
This example’s personalization flow depends on pages/_middleware.tsx (getPersonalizedRewrite rewrites requests there), but that legacy middleware entrypoint was removed in newer Next.js majors, so bumping directly to next@16 disables or breaks that behavior until the middleware is migrated to the supported root middleware pattern. As written, this version change can silently drop personalization rewrites for production requests.
Useful? React with 👍 / 👎.
2 participants
Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.
Snyk changed the following file(s):
starter/personalization-builder-io/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NEXT-15674556
SNYK-JS-NEXT-15674558
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling