[Snyk] Security upgrade next from 12.3.7 to 16.1.7#499
Conversation
…erabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NEXT-15674556 - https://snyk.io/vuln/SNYK-JS-NEXT-15674558
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3249381472
ℹ️ 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".
| "add": "^2.0.6", | ||
| "jose": "^4.4.0", | ||
| "next": "^12.1.0", | ||
| "next": "^16.1.7", |
There was a problem hiding this comment.
Align React major with upgraded Next.js
Upgrading next to ^16.1.7 while leaving react/react-dom on 17.0.2 creates an incompatible dependency set for this example, so fresh installs or builds can fail due to Next 16 peer/runtime expectations not matching React 17. In this commit only next was changed, so the project is left in a broken upgrade state until React (and any dependent libraries) is upgraded in tandem.
Useful? React with 👍 / 👎.
Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.
Snyk changed the following file(s):
edge-middleware/clerk-authentication/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