Skip to content

v2.0.1

Marketplace
Marketplace

Choose a tag to compare

View all tags
@zyga zyga released this 08 Nov 14:59
· 3 commits to main since this release
v2.0.1
1ccddb8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A maintenance release with no change in behaviour: @v2 runs exactly as in v2.0.0, so there is nothing to update in your workflows.

  • Listed on the GitHub Marketplace. The action's description is shorter, to fit the Marketplace's 125-character limit (#12).
  • CI: runs for version tags now find the caches that run saved, so the release's own cache check works on tags too (#9). This only affects this repository's CI, not callers.

New in v2, if you are coming from v1

v2 is a Node.js action that saves the package cache itself at the end of the job (#1), so using it takes one step:

- uses: zyga/setup-pkgproxy@v2
  id: pkgproxy

Upgrading (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. 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.

Better caching:

  • Rolling keys: each job that adds to the cache saves it under a new key and the next job restores the newest, so the cache keeps up with what your jobs download.
  • No needless uploads: a job that added nothing saves nothing.
  • xattrs preserved, in the same pkgproxy-cache-v4 format as v1.2.0, so a v1.2 cache warms v2. Caches from v1.0 and v1.1 start cold once.
  • Job summary showing what was restored, how the cache grew, whether it was saved and why, and pkgproxyctl stats.

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

See the v2.0.0 release for the full notes.

Full Changelog: v2.0.0...v2.0.1

Assets 2
Loading