Android support lands in Turborepo as pnpm sharpens update workflows

Turborepo expands to Android and refines the developer experience

The biggest news this week is that Turborepo now supports Android through Termux, making it possible to run monorepo orchestration directly on mobile devices. This is more than a novelty — it opens the door for CI runners on Android hardware and developers who want to manage repos from tablets. The same release fixes the TUI so the task list can be scrolled with the mouse wheel, and makes releases resumable, a welcome improvement for teams that hit network flakes during long CI runs.

The Android support first appeared in canary.3, which also introduced a major refactoring effort: hashing, caching, microfrontend commands, and run summaries are now backed by package knowledge. This internal shift means Turborepo can make smarter decisions about which tasks need re-execution, a change that will pay off as the refactoring continues. The subsequent canary.4 migrated resolution handling across lockfile parsing, external packages, prune, and global hash inputs, and now task hashes use resolution fingerprints for more accurate caching.

Meanwhile, Turborepo 2.10.7 fixed a critical pnpm pruning issue: turbo prune now preserves root and aliased dependencies, which was breaking builds that relied on those dependencies being available after pruning. It also added support for multiple macOS file watch roots, handy for developers using symlinked directories or custom workspace layouts.

pnpm brings GitHub Actions into the update fold

pnpm shipped five patch versions this week (11.15 through 11.19), culminating in a set of features that make the package manager more useful for CI and release automation. The standout is that pnpm update and pnpm outdated can now update GitHub Actions — if your workflow files reference actions by version, a simple pnpm update will bump them alongside your npm dependencies. Even better, pnpm update can automatically write changesets for the bumps it makes, streamlining the process of shipping dependency updates.

The memory improvements are worth noting: on large workspaces, peak resolution memory has been cut several times over, which translates to faster installs and less pressure on CI runners. The series also introduces publishConfig.name for publishing a package under a different name than its directory, at long last solving a common pain point for monorepo maintainers who want to publish with scoped names while keeping directory names simple. pnpm self-update is now hardened against project-supplied configuration, preventing a malicious package from hijacking the update process, and web-based login works without a TTY, making it easier to authenticate in CI environments.