Skip to content

fix(deps): bump next to 16.4.5 - #550

Merged
sitole merged 1 commit into
mainfrom
sitole/next-16-4-5
Nov 9, 2026
Merged

sitole merged 1 commit into
mainfrom
sitole/next-16-4-5

Conversation

@sitole

@sitole sitole commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

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

  • Pin next and @next/env from 16.3.6 to 16.4.5 in package.json.
  • Update bun.lock with Next.js, env, and SWC packages at 16.4.5.
  • Update sharp and @img packages from 0.35.4 to 0.35.5, as required by Next.js 16.4.5.

Verification

Passed with Bun 1.4.4:

  • bunx bun@1.4.4 install
  • bunx bun@1.4.4 install --frozen-lockfile
  • bunx 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:ci
  • PUBLIC_E2B_DOMAIN=smoke.invalid bun run build — confirmed Next.js 16.4.5; warnings from @opentelemetry/instrumentation-winston and e2b.
  • bunx tsc --noEmit — after the build generated PageProps types.
  • bun run test:unit — 318 tests across 31 files.
  • ./scripts/container-smoke.sh — local image confirmed Next.js 16.4.5.

Not verified

  • Integration tests were not run.
  • Deployed images were not verified because the GCP endpoint at 127.0.0.1:18080 was unavailable.
  • Vanta flagged Next.js 16.3.6 in dashboard image digest c4291f5e0da1b3511a521bf19f302cadfbcf39bf9f5f91ac390a4b33b8f98cbd. This PR and local build do not fix old immutable images. Rollout and scan confirmation follow separately.

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.
@cursor

cursor Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

PR Summary

Medium Risk
Core Next.js framework and image pipeline (sharp) version change; behavior should be close to a patch release but it touches request handling and build tooling.

Overview
Next.js and @next/env are pinned to 16.4.5 (from 16.3.6) so the app is off the affected 16.0.0–16.4.0 releases tied to unauthenticated RCE advisories in image optimization and cached typed-array paths. bun.lock tracks the same bump for next, @next/env, @next/swc-*, and transitively sharp / @img/* at 0.35.5, which Next 16.4.5 requires.

Reviewed by Cursor Bugbot for commit f97607a. Bugbot is set up for automated code reviews on this repo. Configure here.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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: next and @ next/env both move to the exact pin 16.4.5, so they stay in sync.
  • bun.lock: the root workspace entries, the next entry and all eight @ next/swc-* binaries are at 16.4.5. next now needs sharp ^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.

@sitole
sitole merged commit 2f968f0 into main Nov 9, 2026
12 checks passed
@sitole
sitole deleted the sitole/next-16-4-5 branch November 9, 2026 13:37
sitole pushed a commit that referenced this pull request Nov 9, 2026
🤖 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants