🚨 [security] Update all of nextjs 13.5.6 → 14.2.3 (major) #43
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Closed in favor of #45. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-config-next (13.5.6 → 14.2.3)
Sorry, we couldn't find anything useful about this release.
✳️ next (13.5.6 → 14.2.3) · Repo
Security Advisories 🚨
🚨 Next.js Server-Side Request Forgery in Server Actions
Release Notes
14.2.3
14.2.2
14.2.1
14.1.4
14.1.2
14.1.1
14.1.0
14.0.4
14.0.3
14.0.2
14.0.1
14.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
14.2.3
14.2.2
14.2.1
14.1.4
14.1.2
14.1.0
14.0.4
14.0.3
14.0.2
14.0.1
14.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Sorry, we couldn't find anything useful about this release.
Sorry, we couldn't find anything useful about this release.
🆕 @isaacs/cliui (added, 8.0.2)
🆕 @pkgjs/parseargs (added, 0.11.0)
🆕 @swc/counter (added, 0.1.3)
🆕 foreground-child (added, 3.1.1)
🆕 jackspeak (added, 2.3.6)
🆕 minipass (added, 7.1.1)
🆕 path-scurry (added, 1.11.0)
🆕 string-width-cjs (added, npm:string-width@4.2.3)
🆕 strip-ansi-cjs (added, npm:strip-ansi@6.0.1)
🆕 wrap-ansi-cjs (added, npm:wrap-ansi@7.0.0)
🗑️ glob-to-regexp (removed)
🗑️ watchpack (removed)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands