-
-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump next from 14.2.15 to 14.2.21 in /references/nextjs-realtime #1583
base: main
Are you sure you want to change the base?
Bump next from 14.2.15 to 14.2.21 in /references/nextjs-realtime #1583
Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.2.15 to 14.2.21. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.15...v14.2.21) --- updated-dependencies: - dependency-name: next dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
|
WalkthroughThe pull request involves a minor version update of the Next.js dependency in the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -26,7 +26,7 @@ | |||
"clsx": "^2.1.1", | |||
"date-fns": "^4.1.0", | |||
"lucide-react": "^0.451.0", | |||
"next": "14.2.15", | |||
"next": "14.2.21", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Next.js version 14.2.21 needs to be updated to 14.2.22 for latest security patches
The current version bump to 14.2.21 is not sufficient as there's a newer patch version (14.2.22) available in the 14.2.x series. While version 14.2.21 does patch the recent "DoS with Server Actions" vulnerability (as shown in the security advisories), it's recommended to use the latest patch version for all available security fixes.
- Update
next
from"14.2.21"
to"14.2.22"
inreferences/nextjs-realtime/package.json
🔗 Analysis chain
Verify Next.js version and security advisories
The Next.js version bump from 14.2.15 to 14.2.21 looks good. This patch update should only contain bug fixes and security patches.
Let's verify if this is the latest patch version and check for any security advisories:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check latest Next.js version and security advisories
# Check npm for latest versions
npm view next versions --json | jq 'map(select(startswith("14.2."))) | .[-5:]'
# Check for security advisories
gh api graphql -f query='
{
securityVulnerabilities(first: 5, ecosystem: NPM, package: "next") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'
Length of output: 1643
Bumps next from 14.2.15 to 14.2.21.
updated-dependencies:
Closes #
✅ Checklist
Testing
[Describe the steps you took to test this change]
Changelog
[Short description of what has changed]
Screenshots
[Screenshots]
💯
Summary by CodeRabbit