[Snyk] Security upgrade next from 15.3.5 to 15.3.8#18
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request aims to bolster the project's security by updating the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request, automatically generated by Snyk, upgrades the next package from version 15.3.5 to 15.3.8 to resolve two security vulnerabilities. The update is necessary and correctly applied in package.json. However, there is a minor inconsistency in package-lock.json where the next dependency is specified with a caret (^15.3.8) instead of being pinned, which mismatches the intent in package.json. I've left a comment with a suggestion to fix this to ensure dependency resolution is consistent and predictable.
| "@nosecone/next": "1.0.0-beta.9", | ||
| "@oddbird/css-anchor-positioning": "0.6.1", | ||
| "next": "15.3.5", | ||
| "next": "^15.3.8", |
There was a problem hiding this comment.
There's an inconsistency between package.json and package-lock.json. package.json pins the next version to 15.3.8, but here in package-lock.json it's specified with a caret as ^15.3.8. While the resolved version is correct for now, this can lead to confusion and unexpected behavior in the future. To fix this, you should run npm install to regenerate the lock file based on the pinned version in package.json.
| "next": "^15.3.8", | |
| "next": "15.3.8", |
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