Bump locked main branch to address CVE#2761
Merged
Merged
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
chanceaclark
approved these changes
Dec 11, 2025
bookernath
force-pushed
the
bump-main
branch
from
December 11, 2025 23:35
49d49c8 to
78afaf8
Compare
…utes to standardize runtime configuration.
bookernath
force-pushed
the
bump-main
branch
from
December 11, 2025 23:43
c8b6de0 to
b1589b2
Compare
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
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.
What/Why?
Bump next.js version on
mainjust in case anyone still clones this branch.canaryis the best branch to use going forward, but we don't want an oldmainbranch with a CVE`.Testing
Build + preview deployment
Migration
N/A