Repository navigation
Comparing changes
Open a pull request
base repository: vercel/turborepo
base: v2.11.9
head repository: vercel/turborepo
compare: v2.11.10
- 19 commits
- 124 files changed
- 15 contributors
Commits on Oct 16, 2026
-
fix: Allow non-recursive Turbo commands in root tasks (#14814)
Fixes #14795. Root tasks currently reject any script containing the word `turbo`, including `echo turbo` and `turbo boundaries`, even though neither runs tasks. Update the guard to distinguish printed arguments from executable commands and allow known inspection commands. Handle quoted commands, compound scripts, and supported package-manager wrappers while keeping `run`, `watch`, shorthand tasks, and unfamiliar shell syntax guarded. Add regression coverage for both reported failures, inspection commands, genuine recursion, and package scripts that could be mistaken for execution wrappers. Verify recursive scripts are rejected before execution. **Validation:** Linux unit and CLI tests, native Windows execution using a GNU build, Clippy, formatting, and diff checks passed. Windows/MSVC has not been tested.
Configuration menu - View commit details
-
Copy full SHA for 730a98a - Browse repository at this point
Copy the full SHA 730a98aView commit details -
chore: Release Turborepo 2.11.9 (#14824)
## Release v2.11.9 Versioned docs: https://v2-11-9.turborepo.dev ### Changes - chore: Release Turborepo 2.11.8 (#14789) (`d937b9d`) - perf: Prefetch Cargo metadata during lazy graph construction (#14497) (`2a2786c`) - perf: Compute Berry lockfile closures once across workspaces (#14499) (`910886d`) - perf: Check cache hit outputs in place instead of on the blocking pool (#14524) (`ed120d5`) - perf: Speed up Berry lockfile loading (#14500) (`81a81e8`) - perf: Parse bun.lock without building a JSON syntax tree (#14502) (`172d9e9`) - perf: Skip the dry run cache batch window when there is no remote cache (#14505) (`025eb71`) - perf: Emit lockfile closures pre-sorted and cheapen closure interning (#14525) (`2a4812f`) - perf: Reuse configuration derived from turbo.json between the shim and the CLI (#14521) (`cb65c08`) - feat: Report locked tools-only setup plans (#14483) (`ae970f6`) - perf: Compute Bun lockfile closures once across workspaces (#14501) (`778e14a`) - perf: Reuse open parent directories when restoring cache archives (#14506) (`f3747f5`) - perf: Skip dropping the run right before turbo run exits (#14507) (`858990a`) - perf: Match literal input exclusions without compiling globs (#14510) (`1aa874f`) - perf: Copy pruned package files in parallel (#14512) (`2ebac47`) - feat: Report proposed first-lock and refresh setup plans (#14571) (`d12516c`) - perf: Compress large cache archives with multithreaded zstd (#14698) (`5b3d03c`) - perf: Read tracked file stats from directory listings on Windows (#14633) (`7789888`) - perf: Diff changed lockfile resolutions with a merge instead of ordered sets (#14630) (`452c8b7`) - perf: Write dry run text output through one buffered stdout handle (#14625) (`213115d`) - perf: Parse pnpm-workspace.yaml once per command (#14620) (`7ae73f9`) - perf: Write each file trace error to stderr in a single call (#14618) (`4abf82b`) - perf: Reuse glob validation results when re-validating turbo.json in the language server (#14615) (`bd3cda2`) - perf: Keep git subprocesses off the critical path of dry runs (#14610) (`ec761cb`) - perf: Classify watch file changes when they arrive instead of on a 100ms poll (#14600) (`268696e`) - perf: Buffer TUI raw-output spool writes (#14597) (`f8f298a`) - perf: Add the turbo query version key without re-parsing the response (#14592) (`463a689`) - perf: Replay cached task logs in whole-line chunks (#14590) (`255fd13`) - perf: Write each boundaries diagnostic to stderr in a single call (#14587) (`2d990c1`) - perf: Walk leading-globstar input trees in parallel without wax (#14511) (`462cb81`) - perf: Reuse open parent directories when writing cache archives (#14513) (`ac51cd7`) - perf: Index Bun lockfile subgraph lookups instead of rescanning all packages (#14514) (`8d11635`) - perf: Render the pruned lockfile while package files are copied (#14515) (`a5f426b`) - feat: Resolve exact native npm lock cohorts (#14484) (`b5a179d`) - perf: Batch prefixed task output into one write per chunk (#14588) (`92dc725`) - perf: Share one allocation per external package identity (#14528) (`6c2531e`) - perf: Remove quadratic package-name scan from microfrontends discovery (#14527) (`679432d`) - perf: Render file trace errors on several threads (#14623) (`09f6d34`) - perf: Check boundaries packages in parallel again (#14598) (`a38ab01`) - perf: Read PTY child output in 8 KiB chunks (#14594) (`78d5e8f`) - perf: Load each package's tsconfig once when checking boundaries (#14589) (`79570a7`) - perf: Skip the file watcher round trip when checking outputs for new task hashes (#14626) (`94b863f`) - perf: Refresh only memory stats in `turbo info` (#14593) (`622fc20`) - perf: Walk and record prune copy plans in parallel (#14522) (`7928d4f`) - feat: Reconcile sealed clone-local setup selections (#14485) (`ed36803`) - test: Add macOS ACL safety prerequisite for setup state (#14493) (`01f493b`) - fix: Accept Homebrew's bundled npm prefix in setup source preflight (#14566) (`6f024d9`) - feat: Report ignored version manager declarations during setup (#14531) (`8f3a219`) - feat: Provision clone-local setup without lock writes (#14486) (`514c5b8`) - feat: Integrate native npm provisioning into setup (#14491) (`9cc8789`) - test: Check pruned setup outputs through the real CLI (#14529) (`5ab08c6`) - feat: Parse Go toolchain declarations for setup (#14530) (`be0f607`) - feat: Parse root uv version requests for setup (#14533) (`8529794`) - test: Prove Unix process parity for native and npm-wrapped turbo run (#14539) (`159902b`) - feat: Add root-only `turbo setup` policy to turbo.json (#14541) (`64a8a5f`) - test: Interrupt Unix turbo setup through both entrypoints (#14542) (`c0dc146`) - feat: Bootstrap a verified repository-scoped rustup (#14543) (`51b1233`) - feat: Follow approved release CDN redirects in verified downloads (#14557) (`e96b1e0`) - test: Prove native Windows process parity for standalone and npm-wrapped turbo run (#14565) (`fb76400`) - fix: Explain missing Git and non-repository setup roots (#14567) (`c6f671f`) - fix: Keep non-UTF-8 arguments from crashing the turbo shim (#14570) (`28a19ac`) - feat: Install managed tool generations on native Windows (#14582) (`ba28cd7`) - feat: Add the shell hook by default from the POSIX installer (#14608) (`4a85487`) - feat: Accept Corepack SHA-224 package manager pins (#14640) (`f739c30`) - fix: Accept official Bun ZIP metadata in verified archives (#14657) (`b4fe7fa`) - fix: Write turbo.lock as indented JSON (#14738) (`95696a5`) - fix: Accept project .npmrc files with only install-layout settings (#14740) (`15f16ae`) - feat: Define native lifecycle-script policy for dependency setup (#14661) (`5784f11`) - feat: Resolve uv requests to official locked releases (#14537) (`c15f729`) - feat: Install locked uv with repo-scoped launchers (#14538) (`0754979`) - feat: Record official Go release artifacts in turbo.lock (#14532) (`2729bae`) - feat: Create, refresh, and freeze uv selections in turbo setup (#14547) (`bac15a7`) - feat: Resolve root Python requests through managed uv (#14552) (`2625ebd`) - fix: Lock managed Python for every supported architecture (#14691) (`0f3295d`) - feat: Select Linux setup artifacts by detecting the host libc at runtime (#14637) (`0a4bc5c`) - feat: Provision verified Go toolchain archives (#14544) (`15da2ed`) - feat: Provision locked rustup from turbo setup (#14548) (`77fb8eb`) - fix: Keep managed setup working under Ubuntu's default 0002 umask (#14666) (`85f1a46`) - feat: Provision pnpm 11 releases with their module entry points (#14742) (`0a03742`) - fix: Accept npm and pnpm wrapper environments in setup source policy (#14643) (`7b545d5`) - feat: Extract official python-build-standalone archives (#14669) (`dfcdccd`) - feat: Declare additional repository tools in root setup policy (#14574) (`f10cdcb`) - fix: Parse JSX in JavaScript files (#14794) (`8e6c376`) - fix: Complete CI frozen setup behavior (#14492) (`813cfbb`) - feat: Provision tools with plain turbo setup and report skipped dependencies (#14650) (`6b5719a`) - feat: Record trusted setup installations outside the repository (#14494) (`c5691d5`) - feat: Provision pnpm 12 native binaries from verified platform packages (#14743) (`0b20ecd`) - feat: Parse root rust-toolchain files into portable requests (#14550) (`3881ffb`) - feat: Provision locked Python interpreters through managed uv (#14559) (`9730f0a`) - feat: Sync uv workspaces from the committed uv.lock (#14561) (`32b7cd3`) - feat: Resolve Rust toolchain requests to exact locked channels (#14551) (`c52462d`) - feat: Authorize prepared tools from private setup evidence (#14495) (`027983e`) - feat: Install locked Rust toolchains through private rustup (#14562) (`ef05ed9`) - feat: Create and update Rust selections in turbo.lock (#14563) (`65dff32`) - feat: Prefetch locked Cargo dependencies with managed cargo (#14564) (`c2da04e`) - feat: Activate trusted Node and pnpm for task execution (#14508) (`b96a689`) - feat: Enforce managed run compatibility before CLI handoff (#14509) (`c6e79fb`) - fix: Close managed execution authorization gaps (#14516) (`00faa27`) - fix: Preserve informational exits in managed repositories (#14519) (`d83f8ec`) - feat: Reuse trusted installations for offline setup (#14518) (`f994556`) - feat: Add experimental managed Node and pnpm peer capabilities (#14517) (`a506da8`) - feat: Lock additional tool artifacts and detect declaration drift (#14575) (`9bd0143`) - feat: Install additional tools through a generic verified artifact backend (#14577) (`695b772`) - feat: Activate locked uv and Python and check their readiness (#14649) (`715ecd1`) - fix: Precompile managed Python bytecode while staging (#14670) (`f096855`) - feat: Prune setup records for deleted, moved, or re-cloned roots (#14655) (`3f60d68`) - feat: Activate locked Rust toolchains and check their readiness (#14651) (`28afea9`) - feat: Provision locked additional tools from turbo setup (#14581) (`567145b`) - feat: Create and refresh Go entries in turbo.lock during local setup (#14553) (`27c71bb`) - feat: Prefetch Go modules without changing go.mod or go.sum (#14554) (`793dec9`) - feat: Advertise the managed Node/pnpm peer contract on GNU Linux x64 (#14641) (`e539d18`) - feat: Provision locked Yarn classic binaries (#14555) (`c69d6a2`) - feat: Add repository and CLI controls for skipping lifecycle scripts (#14662) (`8fcb0aa`) - feat: Explain whether turbo setup repairs tools or updates the lock (#14654) (`c3b633f`) - feat: Reuse verified tool downloads across repositories (#14535) (`558d101`) - perf: Cache installed tool tree hashes per generation (#14653) (`ad236b2`) - test: Exercise global setup then plain turbo run end to end (#14642) (`5a60b56`) - feat: Apply root setup policy and CLI overrides in turbo setup (#14663) (`a35bde6`) - feat: Pin and verify the xz Rust tarballs rustup downloads (#14771) (`90f44b6`) - feat: Hash locked additional-tool artifact identity portably (#14583) (`17a30c8`) - feat: Provision locked modern Yarn bundles (#14556) (`319a7b2`) - feat: Provision locked Bun binaries without global Bun (#14558) (`37eaa02`) - feat: Provision offline setup from verified cached artifacts (#14540) (`91d21a1`) - feat: Measure and remove inactive managed tool storage (#14549) (`8344022`) - feat: Create and update turbo.lock for Yarn and Bun during local setup (#14560) (`6175fc0`) - feat: Validate installed Yarn and Bun activation plans and checks (#14648) (`7e07545`) - feat: Set up Bun-only repositories without a Node declaration (#14658) (`4763aa1`) - feat: Add a shell hook that activates managed tools in bash and zsh (#14603) (`6ce614d`) - feat: Add an uninstall mode to the POSIX installer (#14636) (`70ab324`) - test: Recover setup killed mid-download and mid-unpack (#14569) (`067223e`) - feat: Route setup downloads through credential-free mirror overrides (#14545) (`fbc28b4`) - test: Race concurrent setup writers over one shared cache (#14573) (`02fdf5c`) - feat: Clean up replaced managed tools automatically during setup (#14652) (`224beba`) - feat: Add the `turbo exec` command surface (#14536) (`50557d1`) - feat: Run `turbo exec` commands with the managed environment (#14568) (`055f182`) - feat: Activate locked Go and check its readiness in turbo setup --check (#14644) (`db7a59a`) - feat: Name the missing Node declaration when --no-lock setup cannot start (#14701) (`5d5d411`) - feat: Add shell hook support for fish and PowerShell (#14606) (`7870baf`) - fix: Run turbo setup in pruned output without a Git repository (#14639) (`6e9908b`) - fix: Accept umask 0002 ancestors of trusted setup records (#14702) (`57184d1`) - fix: Guard managed `turbo exec` local CLI handoff (#14572) (`4e4762b`) - feat: Lock and verify system Node.js and pnpm under verify-system policy (#14664) (`910f7a7`) - feat: Record and authorize trusted setup roots on native Windows (#14659) (`25d0073`) - test: Verify `turbo exec` end to end from nested paths (#14578) (`ef1e09d`) - test: Prove Unix `turbo exec` parity for standalone and npm wrapper (#14580) (`628a06e`) - feat: Provision managed Node and pnpm on native Windows (#14584) (`457f1dc`) - fix: Preserve `turbo exec` behavior for Windows `.cmd` launchers and Ctrl+C (#14646) (`07763e2`) - test: Prove native Windows `turbo exec` entrypoint parity without managed tools (#14660) (`986bd5d`) - fix: Stop native Windows turbo setup on Ctrl+C from either entrypoint (#14591) (`dead697`) - fix: Refuse managed setup on Windows arm64 hosts, including x64 turbo under emulation (#14672) (`76aee36`) - fix: Propose setup plans with every ecosystem's lock resolver (#14744) (`40de283`) - fix: Detect the host libc for managed turbo run (#14710) (`97f284a`) - feat: Add a frozen npm install adapter for setup dependencies (#14718) (`bf6bc06`) - feat: Activate additional tool binaries in managed run and exec (#14706) (`0a7414e`) - feat: Install locked npm dependencies during turbo setup (#14721) (`c4eee00`) - feat: Follow HTTPS redirects for additional-tool artifacts (#14707) (`cd15afd`) - feat: Configure setup mirrors in the root setup policy (#14700) (`a82b7cf`) - feat: Record trusted setup roots for --no-lock installs (#14727) (`3736489`) - feat: Activate and hash --no-lock selections in plain turbo run (#14729) (`463ff19`) - feat: Install additional-tool archives without a top-level folder (#14708) (`887e800`) - feat: Mirror Bun, uv, and Python release downloads (#14714) (`dcd1156`) - feat: Mirror Go and Rust release downloads (#14739) (`03b948c`) - feat: Provision declared npm without lock writes (#14730) (`0409003`) - feat: Activate every managed ecosystem in turbo run, including its own probes (#14711) (`767bbae`) - feat: Download additional tools through the shared cache, offline mode, and a mirror (#14709) (`65a5653`) - feat: Resolve native task commands through managed binaries (#14712) (`fd5f189`) - test: Cover the Unix additional-tool setup, run, and recovery matrix (#14717) (`3e66b8b`) - feat: Qualify additional tools on native Windows x64 (#14731) (`6d2cd4f`) - feat: Use verified system tools in managed turbo run (#14713) (`99755d8`) - test: Exercise managed Go setup then plain turbo run without host Go (#14719) (`9d93333`) - test: Exercise managed Rust setup then plain turbo run without host Rust (#14720) (`0493634`) - test: Exercise managed uv and Python setup then plain turbo run without host Python (#14722) (`c880e8e`) - test: Exercise managed Yarn and Bun setup then plain turbo run without host tools (#14723) (`dcbfb66`) - fix: Let turbo run and turbo exec use verify-system tools on musl hosts (#14751) (`3ee58a1`) - test: Qualify Yarn classic and modern Yarn setup on native Windows x64 (#14746) (`8f85a5e`) - feat: Provision managed uv on native Windows x64 (#14749) (`2bef03b`) - feat: Provision locked Rust toolchains on native Windows x64 (#14752) (`05d681e`) - fix: Kill the command when `turbo exec` is killed (#14757) (`4ffb0ad`) - feat: Provision managed Go from the official Windows x64 zip (#14748) (`803ad4a`) - feat: Provision managed Python on native Windows x64 (#14756) (`4093034`) - feat: Activate managed tools from the PowerShell hook on native Windows x64 (#14747) (`67c4aec`) - feat: Activate managed Go with a plain GOROOT on native Windows (#14754) (`6f94cfc`) - feat: Provision locked Bun on native Windows x64 (#14750) (`2625c71`) - fix: Keep PowerShell hook output ASCII so console code pages cannot corrupt PATH (#14755) (`6e16487`) - feat: Provision pnpm 12 native binaries on native Windows x64 (#14753) (`b5be2f3`) - fix: Kill the local `turbo` when the global `turbo` that handed off is killed (#14785) (`45a8dea`) - feat: Activate managed Rust on native Windows x64 (#14758) (`c4b70ca`) - feat: Activate managed Go from the shell hook on native Windows x64 (#14764) (`d5aeac9`) - fix: Block cache restoration writes to Git metadata (#14808) (`26ccb98`) - feat: Report locked dependency actions in turbo setup plans and checks (#14724) (`85909df`) - feat: Advertise the managed-run peer contract on every claimed platform (#14780) (`409c609`) - fix: Activate managed tools in turbo watch (#14779) (`b0dee21`) - perf: Stamp installed tool trees on native Windows (#14774) (`26ac5de`) - feat: Install pnpm dependencies in frozen mode during setup (#14726) (`849c145`) - feat: Measure setup outcomes through standard telemetry (#14546) (`a6baee9`) - feat: Install Yarn dependencies immutably during setup (#14733) (`12d5101`) - fix: Activate managed tools in commands that discover the repository (#14784) (`dfb8e37`) - feat: Install Bun dependencies from a frozen lock during setup (#14734) (`496489c`) - feat: Sync locked uv workspaces during turbo setup (#14735) (`cbd3ac9`) - fix: Reject Windows prefixed paths during cache restore (#14809) (`6e814c4`) - feat: Prefetch locked Cargo dependencies during turbo setup (#14736) (`65abf4d`) - feat: Prefetch Go modules during turbo setup (#14737) (`c93e489`) - test: Cover managed uv and Python setup on native Windows x64 (#14761) (`14b60e4`) - feat: Prefetch Cargo dependencies and report the MSVC linker on Windows (#14760) (`3e9c10c`) - feat: Install locked dependencies offline from native caches (#14759) (`fc95b6e`) - feat: Prefetch Go modules with managed Go on native Windows (#14762) (`7356a00`) - feat: Install locked JavaScript dependencies on native Windows x64 (#14763) (`d98d962`) - feat: Probe repository-local turbo on Windows and cover pins on every platform (#14781) (`1de7829`) - feat: Export managed runtime variables from the shell hook on every platform (#14802) (`fb29ed6`) - refactor: Route setup's Git queries through an injectable boundary (#14811) (`3e542a0`) - perf: Load each tsconfig once per file trace (#14627) (`1b11a72`) - perf: Overlap reading and compression when writing large cache archives (#14604) (`dbdcdb8`) - perf: Speed up pnpm lockfile pruning and encoding in turbo prune (#14520) (`9ef9ee2`) - perf: Prefetch remote cache artifacts as soon as task hashes are known (#14585) (`aeab1d7`) - perf: Remove the remaining quadratic passes from the Bun prune subgraph (#14523) (`27ed79d`) - perf: Memoize Cargo.lock closures and share resolution identities (#14498) (`f674fb1`) - perf: Match node_modules-style exclusions by path segment instead of compiling globs (#14634) (`c5b05d0`) - perf: Avoid waking the rayon pool for small workspaces (#14602) (`8308fa9`) - perf: Overlap affected change detection with package graph construction (#14496) (`30692b5`) - perf: Find line breaks in task output a block at a time (#14601) (`e53bf84`) - perf: Buffer task log file writes in 64 KiB blocks (#14607) (`e319751`) - perf: Hand lockfile closures to JavaScript resolution as indices (#14596) (`f208320`) - perf: Share each file's text across its trace errors (#14632) (`d07431c`) - fix: Preserve task output after non-zero exits (#14373) (`02d569b`) - perf: Overlap reading and compression when building cache archives for upload (#14617) (`b9aa312`) - perf: Install cache archives locally while they upload (#14622) (`36995e5`) - perf: Skip newline normalization copies for already-normalized TUI output (#14595) (`f05411f`) - chore: Update with-changesets example (#14638) (`a3ef52a`) - fix: Attribute Cargo.lock changes to the crates whose dependencies changed (#14656) (`74c9fbc`) - fix: Stop installing the Unix shell hook automatically (#14813) (`9328416`) - chore: Release Turborepo 2.11.9-canary.1 (#14817) (`a3bcc4a`) - fix: Allow native package manager configuration during setup (#14816) (`9c90852`) - refactor: Remove setup lifecycle script controls (#14818) (`679efb8`) - docs: Use .NET in the multi-language guide (#14793) (`6834819`) - fix(cache): Parallelize dry-run HEAD fallback (#14801) (`78b039e`) - fix: Allow non-recursive Turbo commands in root tasks (#14814) (`730a98a`) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for ee546c6 - Browse repository at this point
Copy the full SHA ee546c6View commit details -
chore(deps): Update dependency @vercel/geistdocs to v2 (#14417)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@vercel/geistdocs](https://redirect.github.com/vercel/geistdocs) ([source](https://redirect.github.com/vercel/geistdocs/tree/HEAD/packages/geistdocs)) | dependencies | major | [`1.28.1` → `2.10.0`](https://renovatebot.com/diffs/npm/@vercel%2fgeistdocs/1.28.1/2.10.0) | Opened by the central geistdocs Renovate in [vercel/geistdocs](https://redirect.github.com/vercel/geistdocs/blob/main/.github/renovate.cjs). An upgrade report comment on this PR lists any code changes the site needs. Push those changes to this branch, then review and merge it like any other PR; it never merges on its own. --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNDAuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjE2NC41IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> --------- Co-authored-by: vercel-gh-bot-2[bot] <282331341+vercel-gh-bot-2[bot]@users.noreply.github.com> Co-authored-by: molebox <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 516f995 - Browse repository at this point
Copy the full SHA 516f995View commit details -
chore: Update with-gatsby example (#14796)
## Summary Update only `examples/with-gatsby` to exact latest stable dependency pins, including Gatsby 5.16.1, Next.js 16.4.0, React 19.3.0, TypeScript 7.0.2, ESLint 10.12.0, Turborepo 2.11.8, and Prettier 3.9.10. Refresh the package-manager pin to pnpm 12.11.2 and the Node engine to >=26.11.1. - Replace legacy ESLint configuration and incompatible TypeScript compiler-API linting with shared flat configs using `eslint-parser-oxc`, retaining Next.js, Turbo, and Prettier integration. - Modernize Next.js TypeScript settings and fix shared UI transpilation; migrate component return types for React 19. - Register dependency-aware lint/type-check tasks and persistent production preview tasks, and add type checking for the shared UI and Next.js app. - Regenerate the pnpm lockfile, explicitly configure approved dependency build scripts, and refresh installation, development, production-preview, and remote-cache instructions. No release-age settings or exclusions are included. ## Browser verification On Node.js 26.11.1, exercised both production apps in Chromium: confirmed React 19 hydration and the shared button without browser errors, then visited Gatsby's 404 page and followed its home link while verifying client-side navigation without a document reload. This specifically checks the upgrade despite Gatsby's transitive router still declaring React 18 peer ranges. Co-authored-by: vercel-gh-bot-3[bot] <282332853+vercel-gh-bot-3[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for ef60d93 - Browse repository at this point
Copy the full SHA ef60d93View commit details -
fix: Avoid pnpm batch-shim shutdown hangs on Windows (#14819)
Fixes #14803. Persistent tasks can hang after Ctrl+C when pnpm is installed through npm on Windows. The app exits, but `pnpm.cmd` stays alive waiting for batch-job confirmation. Recognize npm’s native pnpm launcher and run its `pnpm.exe` directly. Compare the complete shim against the embedded npm-generated fixture before bypassing it so Corepack keeps control of version selection. Existing global-store support remains unchanged. Add Windows regression tests for npm and Corepack shims, unreadable or modified scripts, paths with spaces, and shim-name casing. **Validation** - 14 Windows unit tests passed. LF and CRLF coverage now runs through command selection. - Native Windows CLI checks confirmed shutdown, argument forwarding, and Corepack version selection. - Formatting, Clippy, and diff checks passed. Unrecognized shim templates keep their existing behavior and may still need a second Ctrl+C. Corepack 0.31.0’s wrapper requires a second Ctrl+C on both main and this branch. The original checks used Windows GNU builds and generated layout fixtures. Additional verification used Windows 11 ARM64 MSVC on a clean NTFS checkout. It used an actual npm-generated pnpm 12.6.0 shim in a prefix containing spaces, without an adjacent `node.exe`. One Ctrl+C exited with code 0 and preserved quoted arguments. The directory-fallback test failed as expected when `is_file()` was temporarily weakened to `exists()`. A default Node installer setup has not been tested. --------- Co-authored-by: Anthony Shew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 9c9236e - Browse repository at this point
Copy the full SHA 9c9236eView commit details
Commits on Oct 17, 2026
-
chore(deps): Update dependency @vercel/geistdocs to v2.11.0 (#14832)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@vercel/geistdocs](https://redirect.github.com/vercel/geistdocs) ([source](https://redirect.github.com/vercel/geistdocs/tree/HEAD/packages/geistdocs)) | dependencies | minor | [`2.10.0` → `2.11.0`](https://renovatebot.com/diffs/npm/@vercel%2fgeistdocs/2.10.0/2.11.0) | Opened by the central geistdocs Renovate in [vercel/geistdocs](https://redirect.github.com/vercel/geistdocs/blob/main/.github/renovate.cjs). An upgrade report comment on this PR lists any code changes the site needs. Push those changes to this branch, then review and merge it like any other PR; it never merges on its own. --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNjUuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE2NS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: vercel-gh-bot-3[bot] <282332853+vercel-gh-bot-3[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for bdfbb21 - Browse repository at this point
Copy the full SHA bdfbb21View commit details
Commits on Oct 18, 2026
-
fix: Exclude tool-managed directories from local dependency inputs (#…
…14696) ### Description With native Cargo, Go, or uv support, a `node_modules` directory inside a local dependency changes the hash of every task that depends on it, even though `git status` is clean. Crates and Python packages that ship a small JavaScript build (wasm-pack bindings, docs sites, test tooling) often have one, so dependents miss the cache on any machine that ran an install there. #### Repro Cargo workspace with `app` depending on `lib`, `node_modules` gitignored, `turbo run build --filter=app --dry=json`, comparing `app#build`: | change | `git status` lines | `main` | this PR | | --- | --- | --- | --- | | none | 0 | `fe52c82c3dc16f3d` | `fe52c82c3dc16f3d` | | ignored `crates/lib/node_modules/pkg/index.js` | 0 | `a98936372e8b09a1` ❌ | `fe52c82c3dc16f3d` | | ignored `crates/lib/web/node_modules/x/a.js` | 0 | `9dfe45f4ff06ae3c` ❌ | `fe52c82c3dc16f3d` | | tracked edit `crates/lib/src/lib.rs` | 1 | `85b9dd81eb9b2975` | `85b9dd81eb9b2975` | #### Cause `derived_task_io` in `cargo.rs`, `go.rs`, and `uv.rs` adds each local dependency (and, for workspace-wide tasks, each member) as an explicit `<dir>/**` input glob. The package's own files are hashed from the Git index, but explicit globs walk the filesystem, so ignored files under a dependency get hashed. Each toolchain excluded a different subset: Go `.git` and `.turbo`, Cargo only `.turbo`, uv `.turbo` and Python caches. #### Fix - `toolchain::directory_source_globs` builds the glob for a dependency directory and excludes `.git/**`, `.turbo/**`, and `**/node_modules/**` inside it. Go's existing `.git`/`.turbo` exclusions are the precedent; this adds `node_modules` and applies the same list to all three toolchains. - Cargo's `crate_source_globs`, Go's dependency loop, and uv's dependency and workspace-member globs use it. uv keeps its Python cache exclusions, and Go keeps its binary-name exclusions. - The package's own default (Git index) inputs are unchanged. #### Compatibility Hashes only change for tasks whose dependency directories contain one of those directories; clean checkouts hash the same as before. A build that really reads files from a dependency's `node_modules` (for example `include_str!` into it) would now need to declare them in `inputs`. Those contents normally follow from a lockfile, but a lockfile outside the dependency is not part of these hashes. ### Testing Instructions - `crates/turborepo/tests/cargo_workspace_test.rs`: `test_dependency_crate_node_modules_does_not_change_entrypoint_hash` adds an ignored `node_modules` file to `lib-a` and then edits its source. It fails on `main` (`9395b57566ce8ed6` vs `6f0dd628ed130c80`) and passes here. - Cargo, Go, and uv `derived_task_io` unit tests assert the new exclusions. ``` cargo test -p turborepo-repository --lib cargo test -p turbo --test cargo_workspace_test --test go_workspace_test --test toolchain_scope_test ``` --------- Co-authored-by: Anthony Shew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for db2b83c - Browse repository at this point
Copy the full SHA db2b83cView commit details -
fix: Match git's text=auto binary detection in file hashing (#14697)
## Summary Under `* text=auto`, turbo decided whether a file is binary only by looking for a NUL in the first 8KB. That is git's diff heuristic (`buffer_is_binary`). Git's checkin conversion uses `gather_stats` + `convert_is_binary` in `convert.c` over the whole file. A file counts as binary there if it has a lone CR, a NUL anywhere, or more than one non-printable byte per 128 printable ones (a trailing `^Z` is ignored). So turbo normalized CRLF in content that git stores raw. Two things follow: - **Stale cache hit:** an edit that only adds CRs before LFs gets the committed content's hash, and turbo replays the old outputs. - **Spurious miss:** the same committed bytes hash differently when the file is stat-fresh (index oid) and when it is stat-stale or racy (turbo's normalized hash). ### Reproduction The repo has `* text=auto` and `core.autocrlf=false`. Package `a` has `build: cp data.bin dist/out.bin` with `outputs: ["dist/**"]`. Commit `data.bin`, run `turbo run build`, then rewrite every `\n` in `data.bin` as `\r\n` and run again. `git diff` reports the file as modified in all three cases. | `data.bin` (committed) | git blob before → after | main | this branch | |---|---|---|---| | `a\nb\rc\n` (lone CR) | `73dddfa` → `f272997` | cache hit, stale `dist/out.bin` | cache miss | | NUL after 9000 bytes | `99115d7` → `719c19b` | cache hit, stale `dist/out.bin` | cache miss | | `a\x01\nb\n` (control byte) | `05fca5d` → `2e2d0fe` | cache hit, stale `dist/out.bin` | cache miss | ## Fix - `crlf.rs` classifies bytes the way `gather_stats` does: a 256-entry class table, folded into the existing CRLF-counting scan. It runs only when the attribute is `text=auto`. - Only the non-printable classes are counted; the printable count is derived from the total. Classification stops once a NUL decides the result. Without this, counting every byte made `text=auto` hashing about 2.7x slower. With it, scan plus SHA-1 runs at about 0.82 GB/s on text, against 1.10 GB/s before, and at baseline speed on binary content (release build, Apple M4). - The 8KB `GIT_BINARY_DETECT_LEN` constant is removed. Every hashing entry point already goes through `should_normalize`, so the cache, manual and verification paths agree. ## Known gap (not fixed here) git keeps storing CRLF for a file whose index blob already contains CRLF (`has_crlf_in_index`), which happens when such files were committed before `text=auto` was added. turbo still hashes those as LF when the entry is stale. Handling it needs the index blob, so it is only documented in the `crlf.rs` header. ## Tests - `crlf::tests::test_text_auto_binary_classification_matches_git` compares against `git hash-object --path` for 16 contents. It covers the ratio edge (127/128), `^Z`, and the 64KB read boundary. - `crlf::tests::test_scan_binary_detect_nul_after_first_chunk` - `package_deps::tests::test_text_auto_binary_content_hashes_like_git` runs end to end through `RepoGitIndex` and `verify_candidate`. - All three fail on `main`. - A differential check against git's own `convert.c` logic, over about 80k generated files with mixed read sizes, found no mismatches. I didn't commit it. - `cargo test -p turborepo-scm` and `cargo test -p turbo` pass, and `cargo clippy -p turborepo-scm --all-targets -- -D warnings` is clean. Tested on macOS (Apple Silicon) only; Linux and Windows not tested.
Configuration menu - View commit details
-
Copy full SHA for d154e7e - Browse repository at this point
Copy the full SHA d154e7eView commit details
Commits on Oct 19, 2026
-
fix: Drop @react-router/dev from Remix match list (#14800)
### Description React Router 7/8 in framework mode builds on top of Vite and expects `VITE_*` environment variables. In #14060, `@react-router/dev` was added to Remix's dependency match list. Because Remix takes precedence over Vite, React Router apps were identified as Remix, inferring only `REMIX_*` wildcards and stripping out `VITE_*` in strict mode. This PR drops `@react-router/dev` from the Remix match list, allowing React Router applications using Vite to be properly inferred as Vite (`VITE_*`). Follow-up to #14060 (comment) ### Testing Instructions Ran framework unit tests: ```bash cargo test -p turborepo-frameworks ``` Added test case ensuring `@react-router/dev` + `vite` dependencies match the `vite` framework. Co-authored-by: Pcmhacker-piro <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 3962b47 - Browse repository at this point
Copy the full SHA 3962b47View commit details -
fix: Match package configuration files and directory inputs in task-l…
…evel affected detection (#14804) ### Description With `futureFlags.affectedUsingTaskInputs`, `turbo run --affected`, `turbo query affected` and `turbo ls --affected` skip tasks whose hash changed. CI then reports success without running them. This happens in three cases: - a package's `package.json` or `turbo.json` changes, and the task's `inputs` don't list it; - an input names a directory (`"src"`), and a file inside it changes; - a file is listed and also excluded (`["src/index.ts", "!src/**"]`), and that file changes. #### Repro Two npm packages, `app` depending on `lib`. `build` has `"inputs": ["src/**"]` (`"src"` in the last row) and `dependsOn: ["^build"]`. One commit changes `lib`, then `--base`/`--head` compare the two commits: | change in `lib` | `lib#build` hash, base → head (same on both) | `main`: `run --affected` / `query affected` | this PR | | --- | --- | --- | --- | | edit `scripts.build` in `packages/lib/package.json` | `25c61765f18d3113` → `abab2287ebcf6636` | `[]` / `[]` ❌ | `app#build`, `lib#build` on both | | add `packages/lib/turbo.json` | `25c61765f18d3113` → `05bbd455104f57c5` | `[]` / `[]` ❌ | `app#build`, `lib#build` on both | | `"inputs": ["src"]`, edit `src/index.ts` | `25c61765f18d3113` → `7b3332c417eceeb6` | `[]` / `[]` ❌ | `app#build`, `lib#build` on both | The listed-and-excluded case (`["src/index.ts", "!src/**"]`) is covered by the unit tests below. #### Cause The matcher in `turborepo-types/src/task_input_matching.rs` compiles only the declared `inputs` globs, but the hashers resolve them differently: - In explicit mode, the git hasher always adds `package.json`, `turbo.json` and `turbo.jsonc` with a `stat`, and exclusions don't remove them (`turborepo-scm/src/package_deps.rs`). - The walker expands a literal directory input to `<dir>/**`, expands each exclusion `X` to `X` and `X/**`, and resolves literal inclusions with a `stat` that exclusions don't apply to (`globwalk/src/lib.rs`). `run`, `query`, `ls`, watch and `filterUsingTasks` all share this matcher (`engine/affected.rs`), so they all miss the same tasks. #### Fix - The configuration file list moves to `globwalk::PACKAGE_CONFIG_INPUTS`. The git hasher and the matcher both use it, and hashing is unchanged. - The matcher resolves each input mode the way the hasher does, using the walker's rules (now public in `globwalk`): - **Explicit mode:** config files always match; a literal inclusion also matches everything under it (`expands_directory_inclusion`); exclusions cover `X/**` (`add_trailing_double_star`); a literal inclusion is never removed by an exclusion. - **`$TURBO_DEFAULT$` mode:** package files follow the exclusions as written; files outside the package follow the walk rules. - An exclusion that resolves to `**` (`!$TURBO_ROOT$/**`) is handled like `""`/`.`, so `wax` never receives `**/**`. #### Compatibility Task hashes are byte-identical to `main` (compared on every task in this repository). Only affected selection changes, and it selects more. A `package.json` edit, such as a version bump, now selects that package's tasks, which matches their hashes changing. `["src", "!src/gen"]` no longer selects a task for edits under `src/gen`, which also matches the hash. Not changed here: - the manual (no-git) hasher doesn't add `turbo.jsonc`; - the matcher doesn't apply `fix_glob_pattern`, so `src/a**` still selects every task (over-selection only); - `task-graph/src/visitor/mod.rs` keeps its own copy of the walker rules. ### Testing Instructions - `crates/turborepo-types/src/task_input_matching.rs`: unit tests for config files in explicit and JIT inputs, directory literals, exclusion expansion per mode, literal inclusions vs exclusions, whole-repository exclusions, and inputs with glob syntax. Several fail on `main`. - `crates/turborepo/tests/affected_test.rs`: `test_task_level_affected_iff_task_hash_changes` edits each kind of input. It asserts that a task's `--dry=json` hash changes exactly when `run --affected` and `query affected` select it. ``` cargo test -p turborepo-types -p globwalk -p turborepo-scm cargo test -p turbo --test affected_test ``` `cargo test -p turbo --no-fail-fast` passes except `exec_managed_test`, `setup_run_journey` and `process_launcher_test`, which fail the same way on `main` on this machine. Tested on macOS (Apple Silicon) only; Linux and Windows not tested. --------- Co-authored-by: Anthony Shew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d926d6a - Browse repository at this point
Copy the full SHA d926d6aView commit details -
fix: Parse pnpm 8 single-project lockfiles (#14806)
### Description pnpm 8 writes `lockfileVersion: '6.0'` single-project lockfiles. Their root `dependencies`, `devDependencies` and `optionalDependencies` entries are `{specifier, version}` maps. turbo typed those sections as string maps, so every such lockfile failed to parse with `invalid type: map, expected a string`. pnpm 8 workspaces with `shared-workspace-lockfile=false` write one of these files per package. In those workspaces, every run warns, the tasks have no external dependency hash, and `turbo prune` fails with "Cannot prune without parsed lockfile". pnpm 9 and later write `importers` even in per-package lockfiles and are not affected. Lockfile 5.x root entries were handled in #13928. #### Repro The new fixture `lockfile-tests/fixtures/pnpm8-single-project-lockfiles` (generated with pnpm 8.15.9, `shared-workspace-lockfile=false`): | | `main` | this PR | | --- | --- | --- | | `turbo run build --dry=json` | warns `devDependencies.is-number: invalid type: map, expected a string`; `hashOfExternalDependencies` is empty for `web#build` and `@repo/ui#build` | no warning; `web#build` `b0264f963727a5fb`, `@repo/ui#build` `4d4cb9509bd34118` | | `turbo prune web` | exit 1, `Cannot prune without parsed lockfile.` | exit 0 | | `check-lockfiles --fixture pnpm8-single-project-lockfiles` | fails at prune | 2/2 pass, including pnpm 8.15.9 frozen install of the pruned output | #### Cause In `turborepo-lockfiles/src/pnpm/data.rs`, the root dependency fields of `PnpmLockfile` are `Option<Map<String, String>>`, and `normalize_single_project_lockfile` always builds `DependencyInfo::PreV6`. The fast parser requires `importers`, so these files always go to serde and fail there. The error is downgraded to a warning in the package graph builder and is fatal in prune. #### Fix - Root dependency entries accept both shapes: a version string (5.x) or a `{specifier, version}` map (6.0). - Normalization picks the shape the lockfile version writes, and returns `Error::RootDependencyShape` instead of guessing when they don't match. pnpm's own writer (`@pnpm/lockfile-file` 8.x) always writes maps for 6.0 and never for 5.x, so pnpm-written files never hit this error. - New fixture, covered by the `check-lockfiles` CI job, including pnpm 8.15.9's frozen-lockfile validation of the pruned output. Out of scope: a `5.4-inlineSpecifiers` single-project lockfile (a pnpm 7 experimental format) now parses but yields an empty dependency closure. Shared lockfiles in that format already behave this way on `main`. ### Testing Instructions - `crates/turborepo-lockfiles/src/pnpm/data.rs`: tests for parsing and encoding a 6.0 single-project lockfile, merging per-workspace 6.0 lockfiles, and the shape mismatch error. - `lockfile-tests`: `pnpm check-lockfiles --fixture pnpm8-single-project-lockfiles` fails on `main` (prune) and passes here. ``` cargo test -p turborepo-lockfiles cd lockfile-tests && pnpm check-lockfiles --fixture pnpm8-single-project-lockfiles ``` `cargo test -p turbo --no-fail-fast` passes except `exec_managed_test`, `setup_run_journey` and `process_launcher_test`, which fail the same way on `main` on this machine. Tested on macOS (Apple Silicon) only; Linux and Windows not tested.Configuration menu - View commit details
-
Copy full SHA for 57ecce3 - Browse repository at this point
Copy the full SHA 57ecce3View commit details -
fix: Keep task env vars in the hash when globalEnv excludes inferred …
…vars (#14805) ### Description A `globalEnv` exclusion such as `!NEXT_PUBLIC_*` opts packages out of framework-inferred variables. In a package with a detected framework, it also removed variables the task lists in its own `env` from the task hash. When such a variable is also readable through the builtin pass-through list (`NEXT_*`, `VERCEL_*`, `NODE_OPTIONS`, ...), the task still reads it, but the hash ignores it. Changing the value then replays a stale cache hit. The same `turbo.json` in a package without a detected framework, or with `--framework-inference=false`, hashes the variable correctly. #### Repro ```json { "globalEnv": ["!NEXT_PUBLIC_*"], "tasks": { "build": { "env": ["NEXT_PUBLIC_API_URL"], "outputs": ["dist/**"] } } } ``` `apps/web` depends on `next`, and its build writes `process.env.NEXT_PUBLIC_API_URL` to `dist/config.txt`. Run `turbo run build` with `NEXT_PUBLIC_API_URL=https://preview.example.com`, then again with `https://prod.example.com`: | build | `main` | this PR | | --- | --- | --- | | preview URL | miss `7f60d9b3683628fe` | miss `529bb3f8429b614f` | | prod URL | **hit** `7f60d9b3683628fe`, `dist/config.txt` is the preview URL ❌ | miss `43f5b22baeef590c`, `dist/config.txt` is the prod URL | | same `turbo.json`, `apps/web` without `next` | miss `be5d1d369907c9f4`, then miss `cc34e79e2fd67ea5` | unchanged | #### Cause `calculate_env_vars` in `turborepo-task-hash/src/lib.rs` merges global `!` patterns into the task's user `env` patterns, but only in the framework branch (#11303). `DetailedMap::from_task_env_parts` subtracts user exclusions from the explicit inclusions as well as from the inferred variables. The non-framework branch never applies global exclusions to the task's `env`. #### Fix Global `!` patterns are added to the inference exclusions only, the same way `TURBO_CI_VENDOR_ENV_KEY` exclusions are, and the task's user patterns are its own `env`. The code comment #11303 added says global exclusions "should apply to framework inference". After the fix, a framework package and a plain package with the same `turbo.json` hash the same variables. #### Compatibility - Hashes change only for framework packages where a `globalEnv` exclusion matches a variable the task lists in `env` (including through wildcards), and for their dependents. Those tasks miss the cache once after upgrading. Hashes for every task in this repository are unchanged. - A variable excluded globally but listed in the task's own `env` is now passed to the task. Example: Vite with `"globalEnv": ["!VITE_BUILD_ID"]` and `"env": ["VITE_*"]`. On `main`, `VITE_BUILD_ID` was hidden from that task and unhashed; now it is visible and hashed. - Not changed: with `!NEXT_PUBLIC_*` alone (no task `env`), `NEXT_PUBLIC_*` stays readable through the builtin `NEXT_*` pass-through and unhashed. That is how the documented opt-out works on `main` today. ### Testing Instructions - `crates/turborepo-task-hash/src/lib.rs`: `global_env_exclusions_opt_out_of_inference_but_keep_task_env`. - `crates/turborepo/tests/framework_inference_test.rs`: `test_global_env_exclusion_keeps_task_env_in_hash` changes the declared variable in a Next.js package and expects a different hash. Both fail on `main`, and the existing `test_global_env_exclusion_overrides_inference` still passes. ``` cargo test -p turborepo-task-hash cargo test -p turbo --test framework_inference_test ``` `cargo test -p turbo --no-fail-fast` passes except `exec_managed_test`, `setup_run_journey` and `process_launcher_test`, which fail the same way on `main` on this machine. Tested on macOS (Apple Silicon) only; Linux and Windows not tested. Co-authored-by: PedroRosalba <[email protected]> Co-authored-by: Anthony Shew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 6048038 - Browse repository at this point
Copy the full SHA 6048038View commit details -
docs: Generate the sitemap from Geistdocs sources (#14865)
### Description `sitemap.xml` was built by a Turborepo-only generator that turned content file paths into URLs by hand. It only handled the top-level `index.mdx`, so nine nested index pages are listed as `/index` URLs that 404 (`/docs/core-concepts/index`, `/docs/guides/index`, `/docs/openapi/artifacts/index`, and others). Supersedes #14812, which patched the path handling instead of removing it. This switches `app/sitemap.ts` to the Geistdocs template approach: list `page.url` from the same Fumadocs loaders the routes use (docs, OpenAPI, blog, and extra pages), filtered with `isPageVisibleForSurface(page, "sitemap")`. Sitemap URLs now can't drift from routing. It also removes the Redis crawl state (`lib/sitemap/*`, `/api/crawl-sitemap`, `@upstash/redis`, `linkedom`, and the Upstash env vars in `turbo.json`). The cron that fed it was dropped in the new-site migration (#11415), so the live sitemap currently reports every page's `lastmod` as the request time. `lastModified` now comes from the Geistdocs plugin (frontmatter, then git), and is left out when unknown. Only the default language is listed. `/cn/*` pages serve English fallback content with self-canonicals, and the current sitemap doesn't list them either. ### Testing Instructions 1. Run `next dev` in `apps/docs` and open `/sitemap.xml`. 2. Compare it with https://turborepo.dev/sitemap.xml. I did: both list 145 URLs. The only change is that the nine `/index` URLs become their folder URLs, and each of those returns 200 in production. 3. `pnpm exec tsc --noEmit` passes in `apps/docs`.
Configuration menu - View commit details
-
Copy full SHA for 9330903 - Browse repository at this point
Copy the full SHA 9330903View commit details -
fix: Restore cached symlinks when outputs are already on disk (#14807)
### Description On a local cache hit, `FSCache::fetch` skips extracting the archive when every output recorded in the restore manifest still matches what's on disk. The manifest records only regular files (and directories, when written by `put`). So if a cached symlink was deleted or retargeted, the next run still reports `cache hit` and leaves it missing or pointing at the wrong file. #### Repro `build` writes `dist/a.txt`, `dist/b.txt`, `dist/link -> a.txt` and a dangling `dist/dangling -> missing`, with `"outputs": ["dist/**"]`. Run `turbo run build`, change `dist`, run it again, then compare `dist` with what the task produced: | change before the second run | `main` | this PR | | --- | --- | --- | | `rm dist/link` | `cache hit`, `dist/link` stays missing ❌ | `cache hit`, `dist/link -> a.txt` restored | | `dist/link` retargeted to `b.txt` | `cache hit`, still points at `b.txt` ❌ | `cache hit`, points at `a.txt` again | | `rm dist/dangling` | `cache hit`, stays missing ❌ | `cache hit`, restored | | `rm dist/a.txt` (control) | `cache hit`, restored | `cache hit`, restored | #### Cause `RestoreManifest` has no entry kind for symlinks. Restores and `put` never record them, and the fast path in `fetch` (`validate_all`) only checks the entries that are recorded. A manifest written by a restore doesn't record directories either. #### Fix - `RestoreManifest` records symlinks with their target. `file_matches` checks that the path is still a symlink (`lstat`) and that `readlink` returns the recorded target. - Restores record directories and symlinks as they write them, including symlinks deferred until their targets exist (`restore.rs`). - `CacheWriter::add_files` records the manifest from the entries it archives, including each symlink target. - `Artifact` pairs the archive bytes with that manifest. Downloaded artifacts retain the manifest from restoration. `put_archive` installs the pair without reading outputs again, so an output changed or deleted before local installation cannot become a false cache hit. - Manifests now carry a `version`. One written by an older turbo never short-circuits a whole restore, but its regular files still spare unchanged outputs from being rewritten. - `restore_regular` looks up manifest entries by the `to_unix()` path. This builds on #14506, #14513 and #14524: the in-place hit check and the reused parent directories are unchanged. #### Performance A hit on an unchanged tree now also reads each symlink. With 5,000 symlinks and 5,000 files (debug build, median of 15 runs, 3 blocks), the fast-path hit goes from about 38 ms to about 70 ms. Trees without symlinks do the same work as before. Full restores are unaffected. ### Testing Instructions `crates/turborepo-cache/src/fs.rs`: - `fetch_restores_symlinks_changed_since_put`: deletes and retargets cached symlinks, then expects the fetch to put them back. - `restore_manifest_records_directories_and_symlinks` - `fetch_ignores_manifest_without_version` - `put_archive_restores_*_changed_before_install` and `put_archive_after_restore_restores_changed_*` change or delete files and symlinks before local installation, then expect fetch to restore the archived state. The tests use explicit ordering with no sleeps or concurrent threads. The original three tests fail on `main`. The save-path race tests also failed before the installation fix: changed file contents and retargeted links remained on disk. ``` cargo test -p turborepo-cache ``` `cargo test -p turbo --no-fail-fast` passes except `exec_managed_test`, `setup_run_journey` and `process_launcher_test`, which fail the same way on `main` on this machine. Initial testing was on macOS (Apple Silicon). The cache-crate suite also passes on Linux. Windows remains untested. --------- Co-authored-by: Anthony Shew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 921155f - Browse repository at this point
Copy the full SHA 921155fView commit details
Commits on Oct 20, 2026
-
chore: Remove CODEOWNERS file (#14810)
### Description - Remove `.github/CODEOWNERS`. ### Testing Instructions - Not applicable. Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: anthonyshew <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b42cc68 - Browse repository at this point
Copy the full SHA b42cc68View commit details -
feat: Enable WebMCP for Turborepo docs (#14828)
### Description Enable Geistdocs WebMCP for documentation search and reading the current page. Add the MCP route adapter and reuse the existing search handler. The optional Ask AI tool remains disabled. ```text search_docs /api/mcp existing search handler ``` ### Testing Instructions Verified against the local Next.js dev server: - The WebMCP bridge returned HTTP 200 with JavaScript that includes `search_docs`. - MCP `tools/list` returned `search_docs`. - Calling `search_docs` with query `caching` and locale `en` returned nonempty results without `isError`. Browser-level registration and `read_current_page` remain unverified because no WebMCP-capable browser tool is installed.Configuration menu - View commit details
-
Copy full SHA for af866e5 - Browse repository at this point
Copy the full SHA af866e5View commit details -
fix: Exit quietly when
turbo lsoutput is piped to a closed reader (#……14868) ### Description Fixes #14866. `turbo ls | true`, `turbo ls --output=json | true` and `turbo query ls | true` exit 101 with "Oops! Turbo has crashed", because `ls` prints with `println!`/`cprint!`, which panics on EPIPE. The `turbo run` abort from the report no longer reproduces on 2.11.9, so this covers only the `ls` paths. `ls` now writes to a locked stdout handle and treats a `BrokenPipe` write error as a quiet success. Other write errors are still reported. ### Testing Instructions Added `test_ls_closed_stdout` in `command_ls_test.rs`. It fails on the parent commit and passes with the change (`cargo test -p turbo --test command_ls_test closed_stdout`). I did not run the wider suite or lint targets.
Configuration menu - View commit details
-
Copy full SHA for 9816503 - Browse repository at this point
Copy the full SHA 9816503View commit details -
fix: Distrust compromised eMudhra intermediate certificates (#14876)
### Description Update Turborepo's Rust TLS dependencies in response to the [eMudhra intermediate CA compromise](https://emudhra.we-have-a-problem.com/). ```diff -rustls-webpki 0.103.13 +rustls-webpki 0.103.16 -webpki-roots 1.0.5 +webpki-roots 1.0.10 ``` The patched verifier rejects compromised intermediate public keys even when their roots remain trusted through the system store or custom certificates. The updated root bundle removes the affected emSign root. - Raise the `rustls-webpki` minimum to `0.103.16` and include its required `aws-lc` dependency updates. - Update the `webpki-roots` compatibility package to `0.26.11`, which delegates to `1.0.10`. - Add an offline regression test with captured eMudhra and AAA cross-signed chains, explicitly trusted roots, and a fixed validation date. ### Testing Instructions Ran the regression test in an isolated copy pinned to `rustls-webpki 0.103.13`. It failed because the verifier accepted the compromised chain and returned `ServerCertVerified(())`. With `0.103.16`, the test passes and rejects both captured chains even with their roots explicitly trusted. The test uses checked-in public certificates and does not contact the incident site.
Configuration menu - View commit details
-
Copy full SHA for aaf5a3a - Browse repository at this point
Copy the full SHA aaf5a3aView commit details -
Configuration menu - View commit details
-
Copy full SHA for e521641 - Browse repository at this point
Copy the full SHA e521641View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.11.9...v2.11.10