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 |
| Playwright browsers | Yes |
| Puppeteer browsers | Yes |
| Electron binaries | Yes |
| Cypress binaries | Yes |
| Selenium browsers and drivers | Yes |
| pip | Yes |
| uv | Manual setup |
| Go modules | Yes |
| Cargo | Yes |
| Maven / Gradle | Yes |
| NuGet / .NET | Yes |
| Chocolatey | Yes |
| RubyGems / Bundler | Yes |
| PHP / Composer 2 | Linux |
| Swift / SwiftPM | Yes |
| apt (Ubuntu runners) | Yes |
| apk / dnf / apt (containers) | Manual setup |
It's automatic
Section titled “It's automatic”On Avrea runners, supported package manager registry URLs are pre-configured. Your workflows need no changes for public registries.
Private npm registries require opting in, scope configuration, and a registry token. Private tarballs use the repository cache quota.
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.
Cache stats
Section titled “Cache stats”Playwright and Puppeteer browser downloads appear as separate package-cache rows, with their own hits, misses, bytes, and archive download details. Their activity also contributes to repository cache statistics.
Run and job cache stats show package cache hit rates, bytes served, transfer errors, and recent package or artifact diagnostics when the ecosystem exposes them. See Cache Stats for field definitions and coverage states.