Package Cache
Avrea's package cache sits between your runners and upstream package registries. The first time a package is downloaded, it's fetched from the upstream registry and cached in the colocated cache. Subsequent downloads are served from the cache.
Supported package managers
Section titled “Supported package managers”| Package manager | Auto-configured |
|---|---|
| npm / yarn / pnpm / bun | Yes |
| pip | Yes |
| uv | Manual setup |
| Go modules | Yes |
| Cargo | Yes |
| Maven / Gradle | Yes |
| NuGet / .NET | Yes |
| Chocolatey | Yes |
| RubyGems / Bundler | Yes |
It's automatic
Section titled “It's automatic”On Avrea runners, supported package manager registry URLs are pre-configured. Your workflows need no changes.
The cache.avrea.com hostname used in examples throughout this section resolves
only inside Avrea runners — it points to the colocated cache via the runner's
host file. The URLs are not reachable from a developer laptop.