Skip to content

Upgrade to Next.js 16.2.10#490

Merged
qiao merged 1 commit into
mainfrom
upgrade-next-16
Jul 8, 2026
Merged

Upgrade to Next.js 16.2.10#490
qiao merged 1 commit into
mainfrom
upgrade-next-16

Conversation

@qiao

@qiao qiao commented Jul 7, 2026

Copy link
Copy Markdown
Member

What

Upgrades next 15.3.6 → 16.2.10 with react 19.2.7.

  • middleware.tsproxy.ts, exported function renamed to proxy (middleware is deprecated in 16)
  • Dropped --turbopack from the dev script, it's the default now
  • tsconfig.json / next-env.d.ts changes are auto-applied by next build
  • README: fixed remaining middleware references, Node minimum is 20.9+

No app code changes needed (params was already awaited). Targeting 16.2.10 specifically to pick up the May proxy-bypass fixes, which matter here since the proxy is the tenant routing boundary.

Validation

Verified with pnpm build and a local smoke test: subdomain root rewrites to /s/[subdomain], /admin on a subdomain redirects to /.

Renames middleware.ts to proxy.ts per the v16 deprecation and drops the
--turbopack flag (default in 16). tsconfig.json and next-env.d.ts changes
are auto-applied by next build.
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednext@​15.5.7 ⏵ 16.2.1064 -1100 +759199 +4970
Updated@​types/​react-dom@​19.1.5 ⏵ 19.2.3100 +110075 +185100
Updated@​types/​react@​19.1.4 ⏵ 19.2.171001007992 -2100
Updatedreact@​19.1.0 ⏵ 19.2.7100 +110084 +197100
Updatedreact-dom@​19.1.0 ⏵ 19.2.7100 +110092 +198100

View full report

@qiao qiao changed the title Upgrade to Next.js 16 Upgrade to Next.js 16.2.10 Jul 7, 2026
@qiao
qiao marked this pull request as ready for review July 7, 2026 17:49
@qiao
qiao removed request for ctate and devjiwonchoi July 7, 2026 18:43
@qiao
qiao merged commit ec12e65 into main Jul 8, 2026
2 checks passed
@qiao
qiao deleted the upgrade-next-16 branch July 8, 2026 20:18
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