build(deps): bump next from 16.1.6 to 16.1.7#16
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.1.6 to 16.1.7. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.1.6...v16.1.7) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.7 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Bumps next from 16.1.6 to 16.1.7.
Release notes
Sourced from next's releases.
Commits
bdf3e35v16.1.7dc98c04[backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...9023c0a[backport] Disallow Server Action submissions from privacy-sensitive contexts...36a97b9Allow blocking cross-site dev-only websocket connections from privacy-sensiti...93c3993[backport]: feat(next/image): add lru disk cache and `images.maximumDiskCache...c68d62dBackport documentation fixes for 16.1.x (#90655)5214ac1[backport]: ensure maxPostponedStateSize is always respected (#90060) (#90471)c95e357Backport/docs fixes 16.1.x (#90125)cba6144[backport] Apply server actions transform tonode_modulesin route handlers...3db9063[backport] [Cache Components] Prevent streaming fetch calls from hanging in d...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.
Greptile Summary
This PR is a security-focused Dependabot bump of
nextfrom16.1.6to16.1.7, patching five CVEs in the Next.js framework. The corresponding lockfile is updated with the new@next/*package hashes and a set of transitive dependency upgrades that were pulled in by the resolver.Key changes:
nextbumped to16.1.7inapps/app/package.json, addressing:maxPostponedStateSizenot always respectednext/imageLRU disk cache correctnesshttp-proxyin rewrites@next/swc-*platform binaries updated to16.1.7inpnpm-lock.yamlgraphql(16.12.0 → 16.13.1),caniuse-lite,postcss(8.5.6 → 8.5.8),tough-cookie(6.0.0 → 6.0.1),tldts/tldts-core,type-fest,@img/colour,@emnapi/runtime,baseline-browser-mapping,semver,@babel/runtimevitestnow resolves againstjsdom@26.1.0(down fromjsdom@28.1.0); the olderjsdom@28.1.0package entry (which requirednode ^20.19.0 || ^22.12.0 || >=24.0.0) was removed entirely from the lock file, suggesting a dependency that required it was also removed or relaxedConfidence Score: 5/5
nextversion pin inpackage.json; the rest is a mechanically generated lockfile update. The release is a backport-only patch (16.1.6 → 16.1.7) with no new features, and Dependabot's compatibility score mechanism validates it against the existing test suite. All transitive dependency changes are minor patch-level bumps with no known regressions.Important Files Changed
nextfrom16.1.6to16.1.7; a straightforward single-line version change addressing multiple CVEs.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Dependabot PR: next 16.1.6 → 16.1.7] --> B[apps/app/package.json] A --> C[pnpm-lock.yaml] B --> D["next: 16.1.7 (pinned)"] C --> E["@next/env + @next/swc-* binaries → 16.1.7"] C --> F["Transitive deps updated\n(graphql, caniuse-lite, postcss, tough-cookie, tldts, etc.)"] C --> G["jsdom: 28.1.0 removed\nvitest resolves jsdom@26.1.0"] D --> H[Security patches applied] H --> I["CVE-2026-27977: WebSocket origin blocking"] H --> J["CVE-2026-27978: Server Action privacy context"] H --> K["CVE-2026-27979: maxPostponedStateSize fix"] H --> L["CVE-2026-27980: next/image disk cache"] H --> M["CVE-2026-29057: http-proxy smuggling fix"]Last reviewed commit: "build(deps): bump ne..."