Skip to content

Commit f0b79c5

Browse files
authored
chore(deps): upgrade next 16.2.11 -> 16.2.12 (#6077)
16.2.12 is the current stable (published 2026-07-25) and its entire changelog is two PRs: a docs backport and vercel/next.js#95831, "Fixes to support TypeScript 7". That second one matters here. `apps/sim` declares `typescript: ^7.0.2` and the lockfile resolves 7.0.2, while 16.2.11 predates any TS7 handling — not even the actionable-error guard (#95837), which was never merged. The upstream symptom is `next build` dying with a silent SIGSEGV during its type-check step, because the legacy TypeScript JS API that Next called is gone in TS7. Builds pass today only because Next detects @typescript/native-preview as the compiler and takes a different path, so we are accidentally-working rather than supported. 16.2.12 adds the `experimental.useTypeScriptCli` backend that makes this configuration official. Zero build-performance content in the patch, so this is not a speed change. Bumps all eight pins in lockstep — next, @next/env and the four @next/swc-* binaries at the root, plus the three app/package copies. The swc binaries must move with next: they are platform-gated optionalDependencies, so a version skew or a gate exclusion leaves them out of bun.lock entirely and `bun install --frozen-lockfile` installs no compiler at all (the #5945 failure). Also re-dates the bunfig.toml gate note, which said to drop the next entries on 2026-07-28 — yesterday. 16.2.12 is inside the 7-day window until 2026-08-01, so following that instruction would have blocked this bump and re-triggered the missing-compiler failure. Re-date on future bumps rather than deleting the entries early.
1 parent f78367c commit f0b79c5

6 files changed

Lines changed: 33 additions & 28 deletions

File tree

apps/docs/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
"fumadocs-openapi": "10.8.1",
3030
"fumadocs-ui": "16.8.5",
3131
"lucide-react": "^0.511.0",
32-
"next": "16.2.11",
32+
"next": "16.2.12",
3333
"next-themes": "^0.4.6",
3434
"react": "19.2.4",
3535
"react-dom": "19.2.4",

apps/sim/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@
188188
"mongodb": "6.19.0",
189189
"mysql2": "3.14.3",
190190
"neo4j-driver": "6.0.1",
191-
"next": "16.2.11",
191+
"next": "16.2.12",
192192
"next-mdx-remote": "^6.0.0",
193193
"next-runtime-env": "3.3.0",
194194
"next-themes": "^0.4.6",

bun.lock

Lines changed: 15 additions & 15 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

bunfig.toml

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,15 @@ minimumReleaseAge = 604800
77
# dev builds, so every version is structurally younger than any age gate.
88
# The exactly pinned Pi 0.80.10 packages were vetted for the cloud-review SDK
99
# migration; they age out of the gate on 2026-07-24 — drop these four entries then.
10-
# next@16.2.11, @next/env@16.2.11 and the @next/swc-* binaries are the official Vercel
11-
# security patch for the July 2026 advisories (SSRF, cache confusion, DoS, middleware
12-
# bypass — GHSA-89xv-2m56-2m9x et al.); published 2026-07-21, they age out of the gate on
13-
# 2026-07-28 — drop these entries then. The swc binaries ship in lockstep with next and
10+
# next@16.2.12, @next/env@16.2.12 and the @next/swc-* binaries carry the July 2026 security
11+
# advisories (SSRF, cache confusion, DoS, middleware bypass — GHSA-89xv-2m56-2m9x et al.,
12+
# fixed in 16.2.11) plus the TypeScript 7 support backport (vercel/next.js#95831) that
13+
# 16.2.11 lacks — this repo resolves typescript to 7.x, and on 16.2.11 `next build`'s
14+
# type-check step can die with a silent SIGSEGV because the legacy TS JS API is gone in TS7.
15+
# Published 2026-07-25, they age out of the gate on 2026-08-01 — drop these entries then,
16+
# and re-date this note on any further bump rather than deleting the entries early: removing
17+
# them while the pinned version is still inside the 7-day window blocks the bump outright.
18+
# The swc binaries ship in lockstep with next and
1419
# MUST be excluded alongside it: they are next's platform-gated optionalDependencies, so
1520
# gating them out leaves them absent from bun.lock entirely, and `bun install
1621
# --frozen-lockfile` then installs no compiler at all — next falls back to downloading one

package.json

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,8 @@
7676
"overrides": {
7777
"react": "19.2.4",
7878
"react-dom": "19.2.4",
79-
"next": "16.2.11",
80-
"@next/env": "16.2.11",
79+
"next": "16.2.12",
80+
"@next/env": "16.2.12",
8181
"drizzle-orm": "^0.45.2",
8282
"postgres": "^3.4.5",
8383
"minimatch": "^10.2.5",
@@ -86,10 +86,10 @@
8686
"e2b": "^2.36.1"
8787
},
8888
"optionalDependencies": {
89-
"@next/swc-darwin-arm64": "16.2.11",
90-
"@next/swc-darwin-x64": "16.2.11",
91-
"@next/swc-linux-arm64-gnu": "16.2.11",
92-
"@next/swc-linux-x64-gnu": "16.2.11"
89+
"@next/swc-darwin-arm64": "16.2.12",
90+
"@next/swc-darwin-x64": "16.2.12",
91+
"@next/swc-linux-arm64-gnu": "16.2.12",
92+
"@next/swc-linux-x64-gnu": "16.2.12"
9393
},
9494
"devDependencies": {
9595
"@biomejs/biome": "2.0.0-beta.5",

packages/emcn/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@
8484
"framer-motion": "^12.5.0",
8585
"input-otp": "^1.4.2",
8686
"lucide-react": "^0.511.0",
87-
"next": "16.2.11",
87+
"next": "16.2.12",
8888
"prismjs": "^1.30.0",
8989
"react": "19.2.4",
9090
"react-dom": "19.2.4",

0 commit comments

Comments
 (0)