Skip to content

fix: upgrade turbo version #8259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sriramveeraghanta merged 1 commit into from
Dec 8, 2025
+148 −159
Merged

fix: upgrade turbo version #8259

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/admin/Dockerfile.admin
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ RUN corepack enable pnpm

FROM base AS builder

RUN pnpm add -g turbo@2.6.1
RUN pnpm add -g turbo@2.6.3

COPY . .

Expand Down
2 changes: 1 addition & 1 deletion apps/live/Dockerfile.live
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ RUN apk update
RUN apk add --no-cache libc6-compat
# Set working directory
WORKDIR /app
ARG TURBO_VERSION=2.6.1
ARG TURBO_VERSION=2.6.3
RUN corepack enable pnpm && pnpm add -g turbo@${TURBO_VERSION}
COPY . .
RUN turbo prune --scope=live --docker
Expand Down
2 changes: 1 addition & 1 deletion apps/space/Dockerfile.space
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ RUN corepack enable pnpm

FROM base AS builder

RUN pnpm add -g turbo@2.6.1
RUN pnpm add -g turbo@2.6.3

COPY . .

Expand Down
2 changes: 1 addition & 1 deletion apps/web/Dockerfile.web
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ RUN apk add --no-cache libc6-compat
# Set working directory
WORKDIR /app

ARG TURBO_VERSION=2.6.1
ARG TURBO_VERSION=2.6.3
RUN corepack enable pnpm && pnpm add -g turbo@${TURBO_VERSION}
COPY . .

Expand Down
8 changes: 6 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@
"husky": "9.1.7",
"lint-staged": "16.2.7",
"prettier": "3.7.3",
"turbo": "2.6.1",
"turbo": "2.6.3",
"typescript-eslint": "8.48.0"
},
"lint-staged": {
Expand Down Expand Up @@ -68,11 +68,15 @@
"prosemirror-view": "1.40.0",
"@types/express": "4.17.23",
"typescript": "catalog:",
"vite": "catalog:"
"vite": "catalog:",
"next": "16.0.7"
Comment on lines +71 to +72
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 8, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Next.js version 16.0.7 release date status npm

💡 Result:

Next.js 16.0.7 — published as a security/patch release on December 3, 2025; it’s available on npm and is the patched release Vercel recommends to mitigate the reported RSC/React vulnerability. [1][2][3]

Sources:

  • Next.js blog (security advisory). [1]
  • Snyk package versions (lists 16.0.7 published Dec 3, 2025). [2]
  • jsDocs/npm metadata showing 16.0.7 published. [3]

🌐 Web query:

Next.js 16.0.0 16.x breaking changes migration guide

💡 Result:

Here’s a concise migration guide for Next.js 16 / 16.x (breaking changes + practical steps).

Key breaking changes (what to change)

  1. Async Request APIs — synchronous access removed: cookies(), headers(), draftMode(), and route props like params and searchParams are promises and must be awaited; mark pages/layouts/routes async. Use the codemod to automate many fixes. [1][2]
  2. Turbopack is default — custom webpack() config is ignored by Turbopack; review/remove custom webpack loaders/plugins or opt out to keep Webpack. [1][3]
  3. Removed/renamed features — AMP removed; devIndicators and next lint command removed; serverRuntimeConfig/publicRuntimeConfig removed (use env vars); middleware convention renamed (middleware.ts → proxy or new proxy pattern). [1][3]
  4. New caching model / Cache Components — new opt-in "cache" component patterns and renamed experimental flags; review how caching and PPR were used. [1][3]
  5. Minimum runtime/tooling bumps — Node (>=20.9), TypeScript 5.x and newer React (React 19) requirements; update CI/deploy images. [3][5]

Quick migration steps

  1. Read official upgrade doc and run codemod:
    • npx @next/codemod@canary upgrade latest. This handles many mechanical edits (async APIs, config changes). [1]
  2. Upgrade dependencies:
    • npm install next@latest react@latest react-dom@latest
    • Upgrade Node in CI/deploy to >= Node 20.9 and TypeScript to 5.x if used. [1][3]
  3. Convert Request API usage:
    • Make page/layout/route functions async where they use params/searchParams/cookies/headers and await those values. Run codemod then manually audit complex patterns (hooks, nested components). [1][2]
  4. Handle bundler/config:
    • If you rely on custom webpack features, either port them to Turbopack-compatible approaches or keep using Webpack (explicitly opt out/adjust next.config). Audit next.config for removed options (eslint, devIndicators, runtimeConfig). [1][3]
  5. Update env and runtime config:
    • Replace serverRuntimeConfig/publicRuntimeConfig with environment variables (NEXT_PUBLIC_ for client-visible). [3]
  6. Test thoroughly:
    • Run full build/test on CI, exercise dynamic routes (params/searchParams), middleware/proxy behavior, image optimization, and edge runtimes. Fix missing await errors and Promise propagation. [1][2]
  7. Optional: adopt Cache Components and new features after migration — enable and test incrementally. [1]

Tools & commands

  • Codemod: npx @next/codemod@canary upgrade latest. [1]
  • Typegen (help with new types): npx next typegen. [1]
  • Dependency upgrade: npm install next@latest react@latest react-dom@latest. [1]

References
[1] Next.js — Upgrading: Version 16 (official docs).
[2] "Migrating to Next.js 16" — Michael Pilgram (migration experience, async-API details).
[3] "What's new in Next.js 16" / community guides (Turbopack, config removals, requirements).

Would you like a targeted checklist for a repo (I can scan your package.json/next.config.js and produce exact edits)?

Verify monorepo compatibility with Next.js 16.0.7 before applying override.

Next.js 16.0.7 is a valid release (published December 3, 2025 as a security patch). However, Next.js 16.x introduces significant breaking changes that require verification across all monorepo packages before enforcing this version globally:

  • Async Request APIs (cookies(), headers(), params, searchParams must be awaited)
  • Turbopack now default (custom webpack configs are ignored unless explicitly opted out)
  • Removed features (AMP, devIndicators, serverRuntimeConfig/publicRuntimeConfig, middleware convention changes)
  • Minimum runtime/tooling: Node ≥20.9, TypeScript 5.x, React 19

Confirm that all applications and dependencies in this monorepo are compatible with these changes. Run the Next.js codemod (npx @next/codemod@canary upgrade latest) and test builds thoroughly before merging.

🤖 Prompt for AI Agents 
In package.json around lines 71-72, the pinned Next.js version "16.0.7" may
introduce breaking changes across the monorepo; before approving this override
verify compatibility by (1) auditing each package/app for Next.js 16 breaking
changes (async Request APIs: await cookies(), headers(), params, searchParams;
removed features and middleware changes), (2) ensuring tooling/runtime minimums
(Node ≥20.9, TypeScript 5.x, React 19) are met or upgraded, (3) checking
Turbopack defaults and explicitly opting out where custom webpack is required,
(4) running the Next.js codemod npx @next/codemod@canary upgrade latest and
applying fixes, and (5) performing full CI builds and manual testing of each
app; only update package.json after these checks pass and update any
package-level configs/deps accordingly.

},
"onlyBuiltDependencies": [
"@sentry/cli",
"turbo"
],
"ignoredBuiltDependencies": [
"sharp"
]
},
"packageManager": "pnpm@10.24.0+sha512.01ff8ae71b4419903b65c60fb2dc9d34cf8bb6e06d03bde112ef38f7a34d6904c424ba66bea5cdcf12890230bf39f9580473140ed9c946fef328b6e5238a345a",
Expand Down
Loading
Loading