Repository navigation
fix(deps): upgrade Next.js to 16.4.1 (October 14 security release) - #304
Merged
Merged
Conversation
Patches GHSA-673q-mjm6-r5xr (use cache RCE), CVE-2026-96889 / GHSA-2464-fhr4-w9xw (Image Optimization SVG RCE via sharp) and GHSA-p3m5-59mp-jv5r (Server Actions DoS) in the docs site and the Next.js examples. Next now resolves the fixed sharp 0.35.5. 16.4.1 is younger than the one-day minimumReleaseAge, so its exact versions are excluded until then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 23, 2026
This branch was successfully deployed
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
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.
Summary
Upgrades
nextfrom 16.2.10 to 16.4.1 in the docs site (catalog) and the seven Next.js examples. 16.4.1 is the patched Active LTS release from the October 14 Next.js security update. No 16.2.x patch exists, so this also crosses 16.3 and 16.4.use cachefunctions returning typed arraysNext's
sharpnow resolves to the fixed 0.35.5. 16.2.10 had pulled 0.34.5.Release-age exclusion (temporary)
16.4.1 was published on 2026-10-14 at 17:43 UTC, so pnpm's one-day
minimumReleaseAgeblocks it until 2026-10-15 at about 17:45 UTC.pnpm-workspace.yamladds aminimumReleaseAgeExcludecovering only the exactnext@16.4.1and@next/*@16.4.1versions, with a comment to remove it after that. Patterns are not exempted.Not covered here
evals/agents/fixtures/nextstays on 16.2.10. It's an eval fixture with its own lockfile and release-age gate, and it isn't deployed.@edgestore/server's astro dev dep) still resolvessharp@0.35.3through astro's peer range. That is outside this Next.js advisory.Verification
check:dependencies,format --check,lint,typecheck,build,testnext buildpasses on 16.4.1 fordocsand every Next example (basic-access-controlneeds dummyEDGESTORE_*keys, as before)next starton the docs build:/,/docs/quick-start,/pricingand/blogreturn 200, and the server log has no errors🤖 Generated with Claude Code