Skip to content
Documentation

Docs / Adapter commands / Turborepo

Turborepo adapter

Keep Turbo's task hashes, graph, and outputs. The adapter supplies the remote-cache endpoint and short-lived process credential.

Command
boringcache turbo
Protocol
Turborepo Remote Cache API over /v8/artifacts/*
Action
mode: turbo

How the adapter works

Turbo-native artifacts

Turborepo still hashes task inputs and stores task artifacts through its remote-cache API.

Works outside one provider

Use the same cache from GitHub Actions, another CI runner, or a local shell.

One trust model

Restore from pull requests. Save from trusted jobs.

Set up Turborepo

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

Before the first run

  • Install the repository's Node package manager and Turbo version.
  • Keep task inputs and outputs declared in the Turborepo configuration.
  • Use stable metadata hints; task hashes already identify individual artifacts inside the adapter tag.

Use the same adapter in GitHub Actions

The Action starts the Turbo adapter and gives the later Turbo command its remote-cache environment.

.github/workflows/ci.yml
- uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2
  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.

GitHub Actions reference

Benchmarks

n8n builds the same upstream commits with BoringCache, Depot Cache, GHA Cache and Vercel Remote Cache on the same runner classes.

n8n

Turborepo

Benchmark →

Workflow automation platform. Node.js monorepo with a pnpm workspace.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 24.04 x86-64

BoringCache
1 min 57 s 30 builds
Depot Cache
1 min 59 s 30 builds
GHA Cache
2 min 2 s 30 builds
Vercel Remote Cache
1 min 57 s 30 builds
Same CPU model

Builds of one commit can land on different CPU models. These ratios use only the build pairs where both caches ran on the same model; above 1.00× means BoringCache's total time over those pairs was lower.

Depot Cache vs BoringCache
1.03× · 10 of 30
GHA Cache vs BoringCache
1.05× · 7 of 30
Vercel Remote Cache vs BoringCache
0.97× · 8 of 30
6 CPU models recorded
BoringCache · Remote cache
AMD EPYC 7763 (15 builds) · AMD EPYC 9V45 (6 builds) · AMD EPYC 9V74 (4 builds) · Intel Xeon Platinum 8573C (3 builds) · Intel Xeon Platinum 8370C (2 builds)
Depot Cache
AMD EPYC 7763 (14 builds) · AMD EPYC 9V74 (6 builds) · AMD EPYC 9V45 (4 builds) · Intel Xeon 6973P-C (3 builds) · Intel Xeon Platinum 8573C (2 builds) · Intel Xeon Platinum 8370C (1 build)
GHA Cache · Local cache directory restored and saved by actions/cache
AMD EPYC 7763 (16 builds) · AMD EPYC 9V45 (7 builds) · AMD EPYC 9V74 (4 builds) · Intel Xeon Platinum 8573C (2 builds) · Intel Xeon Platinum 8370C (1 build)
Vercel Remote Cache
AMD EPYC 7763 (15 builds) · AMD EPYC 9V74 (7 builds) · AMD EPYC 9V45 (6 builds) · Intel Xeon 6973P-C (1 build) · Intel Xeon Platinum 8573C (1 build)
Cold and warm builds

Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.

One cold and warm build per cache
Cache Cold Warm CPU
BoringCache Remote cache 2 min 59 s 49.4 s Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V45
Depot Cache 2 min 43 s 43.6 s AMD EPYC 7763 Different CPU
GHA Cache Local cache directory restored and saved by actions/cache 2 min 35 s 36.7 s Cold: AMD EPYC 9V74 · Warm: AMD EPYC 7763 Different CPU
Vercel Remote Cache 2 min 38 s 46.4 s Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 7763 Different CPU

Cache hits

BoringCache · GitHub runner · 4 vCPU

77.0% of 2,225 lookups over 30 builds

Served from the runner
Under 1 ms per read
Read from cache
704 MB

Tool reference

Check the tool's own reference when you need cache-key rules, build settings, or version-specific behavior.

All adapter commands

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.