fix(nextjs): update Next.js versions to patch vulnerability#30574
Merged
fix(nextjs): update Next.js versions to patch vulnerability#30574
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
|
View your CI Pipeline Execution ↗ for commit 6b8c7c9.
☁️ Nx Cloud last updated this comment at |
ndcunningham
approved these changes
Apr 1, 2025
jaysoo
added a commit
that referenced
this pull request
Apr 2, 2025
There is a critical vulnerability with Next.js. This PR updates both the v14 and v15 versions to ensure users are on the latest patched versions. For new projects, it should already be using the latest patch within the minor version, since we default to `~` range. This will ensure that existing projects that did not update yet is updated to the secure versions. See: GHSA-f82v-jwr5-mffw <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior Next.js versions for existing projects may be using vulnerable versions. ## Expected Behavior Migrate existing Next.js projects to patched and secure versions. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is a critical vulnerability with Next.js. This PR updates both the v14 and v15 versions to ensure users are on the latest patched versions.
For new projects, it should already be using the latest patch within the minor version, since we default to
~range. This will ensure that existing projects that did not update yet is updated to the secure versions.See: GHSA-f82v-jwr5-mffw
Current Behavior
Next.js versions for existing projects may be using vulnerable versions.
Expected Behavior
Migrate existing Next.js projects to patched and secure versions.
Related Issue(s)
Fixes #