Turborepo's polyglot push meets pnpm's Python ambitions

Turborepo goes polyglot

The biggest story of the week is Turborepo's steady expansion beyond Node workspaces. Python virtual environments and uv workspace metadata are now first-class inputs, with uv lockfile affectedness properly scoped and a clear explanation when uv task caching is disabled. From there the team layered on static repository discovery with safe affected candidates and derived short names for Go workspace packages, then made Cargo and uv affectedness inferrable from static package inputs — so a Rust or Python package change can now drive the same task graph that JS packages already did. Go handling got its own fixes along the way, including per-module formatting and verification.

Alongside the language work, Turborepo made its query surface smarter: package queries and pruning are now task-aware, and compact task planning is exposed through turbo query, which also brought Remix framework inference, a NUXT_ENV_* wildcard, and NEXT_DEPLOYMENT_ID detection for Next.js.

Turborepo 2.11 lands

The 2.11 line shipped and then stabilized quickly. esbuild builds are allowed for pnpm generators again, and repeatable CLI flags were restored after they stopped accepting repeated values — the same fix carried into the 2.11.3 canaries, which also stop spurious microfrontend polyrepo warnings and refactor the run and execution selector DTOs.

Co-located packages got attention too: they're now inferred from the current working directory, with change owners preserved and task logs isolated, plus fixes for lazy native workspace metadata discovery, Go default binary output paths, and pnpm usage in non-monorepo deployments. Pruning stopped dropping task env mode, and the team bumped tar in @turbo/releaser to close a CVE.