Repository navigation
fix(deps): bump next to 16.4.5 - #550
Conversation
Next.js 16.0.0 through 16.4.0 are affected by GHSA-2464-fhr4-w9xw and GHSA-673q-mjm6-r5xr. The first patched 16.x release is 16.4.1; 16.4.5 is the current latest release.
PR SummaryMedium Risk Overview Reviewed by Cursor Bugbot for commit f97607a. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
I reviewed this dependency bump and found no bugs. It is a minor-version framework upgrade (Next 16.3 to 16.4), and CODEOWNERS covers every path in the repo, so a code owner should still take a look.
What was reviewed:
- package.json:
nextand@ next/envboth move to the exact pin 16.4.5, so they stay in sync. - bun.lock: the root workspace entries, the
nextentry and all eight@ next/swc-*binaries are at 16.4.5.nextnow needssharp ^0.35.5, and the lock resolves it to 0.35.5. All@ img/sharp-*entries are at 0.35.5 and all libvips entries at 1.3.4. No unrelated packages changed. - Not done: the integration tests were not run, and Next 16.4 behavior changes were not checked against the app. The PR description says the same.
Extended reasoning...
The change only touches package.json and bun.lock. It bumps Next.js and @ next/env from 16.3.6 to 16.4.5 and sharp from 0.35.4 to 0.35.5, and no application code changes. No auth, injection or data-exposure code is touched. The bump is meant to pick up fixes for the Next.js RCE advisories. I read through the lockfile and it matches package.json. I deferred instead of approving because the repo CODEOWNERS file assigns every path (*) to named owners. Also, a minor framework release can change runtime behavior that a version-pin review can't check.
🤖 I have created a release *beep* *boop* --- ## [0.5.2](v0.5.1...v0.5.2) (2026-11-09) ### Bug Fixes * **deps:** bump next to 16.4.5 ([#550](#550)) ([2f968f0](2f968f0)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: e2b-generated-code-auto-fixer[bot] <257264331+e2b-generated-code-auto-fixer[bot]@users.noreply.github.com>
Summary
Upgrade Next.js to 16.4.5 to address GHSA-2464-fhr4-w9xw and GHSA-673q-mjm6-r5xr. Both advisories were first patched in 16.4.1.
Changes
nextand@next/envfrom16.3.6to16.4.5inpackage.json.bun.lockwith Next.js, env, and SWC packages at16.4.5.sharpand@imgpackages from0.35.4to0.35.5, as required by Next.js 16.4.5.Verification
Passed with Bun 1.4.4:
bunx bun@1.4.4 installbunx bun@1.4.4 install --frozen-lockfilebunx biome ci --formatter-enabled=false --linter-enabled=true .— 0 errors, 131 warnings, 1 info; not compared against the baseline.bunx biome check --linter-enabled=false --assist-enabled=true .bun run knip:ciPUBLIC_E2B_DOMAIN=smoke.invalid bun run build— confirmed Next.js 16.4.5; warnings from@opentelemetry/instrumentation-winstonande2b.bunx tsc --noEmit— after the build generatedPagePropstypes.bun run test:unit— 318 tests across 31 files../scripts/container-smoke.sh— local image confirmed Next.js 16.4.5.Not verified
127.0.0.1:18080was unavailable.c4291f5e0da1b3511a521bf19f302cadfbcf39bf9f5f91ac390a4b33b8f98cbd. This PR and local build do not fix old immutable images. Rollout and scan confirmation follow separately.