Skip to content

v2.0.0

Choose a tag to compare

View all tags
@zyga zyga released this 08 Nov 12:51
· 6 commits to main since this release
v2.0.0
7f0db60
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

setup-pkgproxy is now a Node.js action that saves the package cache itself at the end of the job (#1). Using it takes one step:

on:
  push:
    branches: [main]   # only the default branch saves the cache, see below
  pull_request:
# ...
- uses: zyga/setup-pkgproxy@v2
  id: pkgproxy

Upgrading from v1 (details in the README's "Upgrading from v1"):

  • Delete your "Prepare pkgproxy cache for saving" and actions/cache/save steps. A post step stops pkgproxy and saves the cache, whether the job passed, failed or was cancelled.
  • Only the default branch saves the cache, by default (save-package-cache: default-branch | always | never). Pull requests and other branches restore the default branch's cache, but never save their own: a PR's copy would only help that PR, while taking room (several hundred MB per snap build) that would evict the default branch's. If your workflow runs only on pull_request, add a push trigger for the default branch, or nothing is ever saved.
  • Outputs: package-cache-hit, package-cache-key-success and package-cache-key-partial are replaced by package-cache-restored-key and package-cache-key.

How the cache is kept:

  • Rolling keys: each job that adds to the cache saves it under a key of its own, and the next job restores the newest one, so the cache keeps up with what your jobs download instead of freezing at its first save.
  • No needless uploads: a job that added nothing saves nothing.
  • xattrs preserved: the cache is saved as an archive made with tar --xattrs, ready for pkgproxy 0.12, under pkgproxy-cache-v4, the same format and prefix as v1.2.0. A v1.2 cache warms v2, but caches from v1.0 and v1.1 start cold once.
  • Job summary: shows what was restored, how the cache grew, whether it was saved and why, and pkgproxyctl stats.

Also:

  • pkgproxy v0.11.0.
  • Go: taken from the runner's tool cache, or downloaded from go.dev and checked against its SHA-256.
  • Clean checkout: the built binary is cached outside your checkout.

v1 stays maintained on releases/v1 (v1.2.0 is out alongside this release).

Assets 2
Loading