Turbo-native artifacts
Turborepo still hashes task inputs and stores task artifacts through its remote-cache API.
Getting started
Guides
On this page
Docs / Adapter commands / Turborepo
Keep Turbo's task hashes, graph, and outputs. The adapter supplies the remote-cache endpoint and short-lived process credential.
Turborepo still hashes task inputs and stores task artifacts through its remote-cache API.
Use the same cache from GitHub Actions, another CI runner, or a local shell.
Restore from pull requests. Save from trusted jobs.
Keep the command and cache tag in .boringcache.toml, then use the same boringcache turbo entrypoint locally and in CI.
[adapters.turbo] tag = "turbo-cache" command = ["turbo", "run", "build"] # Run: boringcache turbo
The Action starts the Turbo adapter and gives the later Turbo command its remote-cache environment.
- uses: boringcache/one@f0fb9b2d926a32b10c543e92093ba00c5a291b79 # v1.33.0 with: trust-policy: auto mode: turbo - run: pnpm turbo run build
Approve the repository through Connect CI and grant the job contents: read and id-token: write. The Action uses that Machine connection. Pull requests restore by default; trusted jobs may publish. See the authentication example in the GitHub Actions reference for scoped credentials when OIDC is unavailable.
n8n · Turbo remote cache.
70–94%
BoringCache stored 70–94% less cache data across public Go, Gradle, Maven, Nx, Turbo, and sccache comparisons.
Open run →Check the tool's own reference when you need cache-key rules, build settings, or version-specific behavior.
Compare every supported command, protocol, and Action mode in one place.
Adapter command index →Need help or found something unclear? Open an issue or browse the CLI repo.
We use cookies to understand how people use BoringCache. Learn more