pnpm 12.4 installs npm, Cargo and Python dependencies from one workspace and one lockfile pass

Sources: release notes, HN discussion
Summary: Setting cargo.enabled and python.enabled in pnpm-workspace.yaml lets one pnpm install resolve all three ecosystems, each keeping its own semantics: crates go to Cargo.toml and Cargo.lock and are vendored through .cargo/config.toml, Python goes to pyproject.toml and a standard pylock.toml with a managed per-project .venv on PATH. What is shared sits below the ecosystem boundary, meaning one HTTP and authentication budget, one verified-artifact ingestion path and one content-addressable store, with frozen and offline installs working for all three. The release also adds pnpm pipeline, which runs a workspace task graph the way CI would and continues past the first failure, and ships binaries for Android arm64 and x64, FreeBSD x64, and Linux ppc64le, s390x and RISC-V.
Why it matters: A polyglot repository can drop separate install, cache and authentication paths for three package managers, at the cost of settings the maintainers state may still change.
Follow-up: Whether the Cargo and Python workspace settings stabilize or change shape in a later release.