Skip to content

chore: bump Next.js from 16.3.4 to 16.3.5 - #16

Merged
smaege merged 1 commit into
mainfrom
cursor/nexus-storefront-modernization-6b83
Sep 21, 2026
Merged

smaege merged 1 commit into
mainfrom
cursor/nexus-storefront-modernization-6b83

Conversation

@cursor

@cursor cursor Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Track

Weekly keep-modern: patch/minor dependency bumps. pnpm format:check is already clean on main (format-gate PR #10), so this run takes the next highest-value track.

Why

next@16.3.4 is one Active LTS patch behind v16.3.5 (2026-09-11). This storefront uses next/image for product, cart, search, and layout images, so the disk-cache hardening is in scope.

Changelog (16.3.4 → 16.3.5)

Patch-only backport. No major migration, no middleware.ts reintroduction (proxy.ts stays).

  • next/image: skip 0-byte entries when initializing the disk LRU cache (#98185) — avoids a poisoned cache singleton from a single empty file.
  • next/image: reject empty images when reading/writing the disk cache (#98186).
  • Emit whole-app server NFTs when output: 'standalone' is used with an adapter (#98167) — we do not set output: 'standalone'.
  • Add CSP nonce to script tags of loading and template files (#98403).
  • Fix use cache prerender signal retention (#98448) — we do not use use cache yet.

Bumps

Package From To Notes
next 16.3.4 16.3.5 Patch. proxy.ts still registered as Proxy (Middleware).

Highlighted packages already at latest in-range: react/react-dom 19.2.8, @finqu/storefront-sdk 1.3.0, @puckeditor/core 0.21.3, tailwindcss 4.3.3.

Intentionally not bumped

  • React 19.3.0 — Next 16.3.5 still peers ^18.2.0 || ^19.0.0 with no 19.3 callout. Stay on 19.2.8 until Next documents it.
  • Puck 0.23 — SDK 1.3 still peers @puckeditor/core@^0.21.0 (^0.21 does not include 0.22/0.23).
  • lucide-react 1.x, @finqu/cli 3.x, typescript 7.x — majors without a migration pass.

Verification

  • pnpm format:check passes.
  • pnpm typecheck passes once .storefront/ is generated (finqu storefront build --components=./blocks). That directory is gitignored and not in this PR.
  • next build on 16.3.5 compiles; all routes remain dynamic; Proxy still detected. Live storefront was not smoked (no Finqu credentials in this environment).

Follow-ups

  • Refresh Finqu agent skills, or add optimizePackageImports for lucide-react.
  • Puck 0.23 after the SDK raises its peer range.
  • React 19.3 once Next 16.3.x (or 16.4) documents support.
Open in Web View Automation 

Patch-only Active LTS update: next/image disk-cache hardening, CSP nonce on loading scripts, and a use cache prerender-signal fix. React 19.3 and Puck 0.23 remain skipped.

Co-authored-by: Miikka Aho <smaege@users.noreply.github.com>
@vercel

vercel Bot commented Sep 17, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
theme-headless-nexus Ready Ready Preview Sep 17, 2026 6:19am UTC

Request Review

@smaege
smaege marked this pull request as ready for review September 21, 2026 07:59
@smaege
smaege merged commit 1ee8c64 into main Sep 21, 2026
3 checks passed
@smaege
smaege deleted the cursor/nexus-storefront-modernization-6b83 branch September 21, 2026 07:59

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Left a non-blocking comment: GitHub blocked approval because this is a self-authored Cursor PR, and Cursor Bugbot was not present after the first check poll. Remaining signals were clean; no reviewers were assigned.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

This branch was successfully deployed

1 active deployment
Preview — 02eece5d Deployed Sep 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants