[Snyk] Security upgrade next from 15.2.0-canary.31 to 15.2.8#29
[Snyk] Security upgrade next from 15.2.0-canary.31 to 15.2.8#29ClementBobin wants to merge 1 commit intomainfrom
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NEXT-14400636 - https://snyk.io/vuln/SNYK-JS-NEXT-14400644
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
This PR upgrades Next.js from version 15.2.0-canary.31 (a pre-release/canary build) to 15.2.8 (a stable release) to address two security vulnerabilities: a high-severity deserialization of untrusted data issue (SNYK-JS-NEXT-14400636) and a medium-severity exposure of sensitive system information issue (SNYK-JS-NEXT-14400644).
Key Changes:
- Upgrades Next.js from canary version 15.2.0-canary.31 to stable version 15.2.8
- Updates
@next/envpackage to version 15.2.8 - Updates all platform-specific SWC compiler packages to version 15.2.5
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| package.json | Updates the Next.js dependency version from ^15.2.0-canary.31 to ^15.2.8 |
| package-lock.json | Updates resolved versions and integrity hashes for Next.js core package, @next/env, and all platform-specific SWC compiler binaries |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NEXT-14400636
SNYK-JS-NEXT-14400644
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:
🦉 Deserialization of Untrusted Data