🔧 chore[security]: upgrade next#1
Closed
iamrajjoshi wants to merge 1 commit into
Closed
Conversation
iamrajjoshi
force-pushed
the
raj--security--next-may-2026
branch
from
6d66ecd to
3329f55
Compare
Owner
Author
|
Closing in favor of upstream PR: getsentry#31 |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of the change
Upgrade Next.js from 15.4.7 to 15.5.18 to pick up the May 2026 security release. Also align eslint-config-next with the patched Next.js version.
Ticket:
Test plan
Lint and production build both pass locally.
Loom or screenshots
Considerations
This follows Vercel’s May 7, 2026 advisory for Next.js 15.x versions <=15.5.17. Local validation still shows the pre-existing Next.js workspace-root warning caused by /Users/raj/package-lock.json being detected above this worktree.