Restore and save dependency caches on Avrea runners. Use @v1 when
switching from actions/cache:
- uses: avrea-com/cache@v1
with:
path: ~/.cache/my-tool
key: dependencies-${{ runner.os }}-${{ hashFiles('lockfile') }}
restore-keys: dependencies-${{ runner.os }}-The combined action restores during the main step and saves after a
successful job. Cache service errors warn and continue. An exact hit skips
saving; fail-on-cache-miss: true fails when no entry is found.
Use avrea-com/cache/restore@v1 and avrea-com/cache/save@v1 for separate
steps. Restore exposes cache-hit, cache-primary-key, and
cache-matched-key. The combined action exposes cache-hit. A complete
miss leaves cache-hit unset; a prefix match sets it to false.
Inputs follow actions/cache v6.1.0.
upload-concurrency and download-concurrency default to 8 and 32.
upload-chunk-size selects an Avrea upload part size, bounded to 5–64 MiB.
enableCrossOsArchive: true lets Windows share compatible cache archives
with Linux and macOS, matching upstream's version hashing. Use portable
paths and cache contents when sharing across operating systems.
The deprecated save-always input has no effect, matching upstream.
Caches use the same keys, version hashes and archive format as upstream cache actions using the Avrea proxy. The native client requires an updated Avrea host with the parts upload protocol.
Cache paths may be outside the workspace, including ~/.cache. Paths,
symlinks and hard links follow upstream cache behavior, including link
targets outside the selected paths. The job's filesystem permissions apply.
This action requires the preinstalled Avrea runner binary. It does not work on GitHub-hosted runners and does not download a binary. The native binary and its source are maintained in Avrea's private repository. Only the manifests, invocation shims, documentation and their MIT license are public.