mirror of
https://github.com/pnpm/action-setup.git
synced 2026-08-14 14:02:10 +08:00
feat: cache the lockfile verification log regardless of cache
The log is under a kilobyte and pnpm writes it on every install, not only where supply-chain policies are configured: the integrity and tarball-URL checks are unconditional. A job that starts without it re-checks every lockfile entry against the registry — on a ~2000-entry lockfile with a warm store, 13.5s vs 1.5s with `minimumReleaseAge` and `trustPolicy` configured, and still 6.7s vs 1.6s with no policies at all. Tying that to the `cache` input made the common case slow for no saving worth counting, so the log is now restored and saved on its own key whether or not the store is cached. `cache` goes back to meaning what its name says.
This commit is contained in:
+3
-3
@@ -17,9 +17,9 @@ inputs:
|
||||
default: 'null'
|
||||
cache:
|
||||
description: |
|
||||
Whether to cache the pnpm store directory and, on pnpm v11 and newer,
|
||||
the results of pnpm's lockfile verification against the configured
|
||||
supply-chain policies. Both are keyed on the lockfile's content hash.
|
||||
Whether to cache the pnpm store directory, keyed on the lockfile's
|
||||
content hash. On pnpm v11 and newer, the results of pnpm's lockfile
|
||||
verification are cached either way — see the README.
|
||||
required: false
|
||||
default: 'false'
|
||||
cache_dependency_path:
|
||||
|
||||
Reference in New Issue
Block a user