fix(deps): bump Next.js 16.1.6 → 16.2.10 to clear high security advisories - #19
Merged
Merged
Conversation
…sories npm audit flagged next@16.1.6 with 2 high + several moderate advisories, including middleware/proxy bypass variants (GHSA-267c-6grr-h53f, GHSA-26hh-7cqf-hhc6, GHSA-492v-c6pp-mqqv), RSC cache poisoning (GHSA-wfc6-r584-vfw7, GHSA-vfv6-92ff-j949), and a batch of DoS issues. 16.2.10 (current stable) clears every direct Next.js advisory. eslint-config-next bumped in lockstep. Lockfile regenerated with --include=optional so the Linux-native optionals (@rollup/rollup-linux-*, @emnapi/*, swc binaries) stay present for CI's npm ci on Linux; verified locally with a clean-room npm ci + full build + test run. Known remaining (not addressed here): - drizzle-orm < 0.45.2 high (GHSA-gpj5-g38j-94v9) — separate bump. - moderate XSS in Next's bundled postcss copy — fixed upstream only in the 16.3 canary line; not worth overriding a framework-pinned internal. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
npm audit flagged next@16.1.6 with 2 high + several moderate advisories,
including middleware/proxy bypass variants (GHSA-267c-6grr-h53f,
GHSA-26hh-7cqf-hhc6, GHSA-492v-c6pp-mqqv), RSC cache poisoning
(GHSA-wfc6-r584-vfw7, GHSA-vfv6-92ff-j949), and a batch of DoS issues.
16.2.10 (current stable) clears every direct Next.js advisory.
eslint-config-next bumped in lockstep. Lockfile regenerated with
--include=optional so the Linux-native optionals (@rollup/rollup-linux-,
@emnapi/, swc binaries) stay present for CI's npm ci on Linux; verified
locally with a clean-room npm ci + full build + test run.
Known remaining (not addressed here):
the 16.3 canary line; not worth overriding a framework-pinned internal.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com