Debug-action-cache Upd Jun 2026

You cannot browse the remote cache directly (unless using self-hosted runners with local storage). However, you can force a debug step after restoration.

Are you experiencing , or is the cache loading stale/corrupted data ? Share public link

Use unique keys per job ( matrix ) to avoid this. debug-action-cache

: Always provide a fallback pattern using restore-keys . If an exact match for package-lock.json fails, falling back to a generic $ runner.os -node- prefix allows the runner to download most dependencies, updating only the newly added packages.

When debug logging is enabled, your Action logs will include these specific markers: Description ##[debug]Resolved Keys: Shows the actual string used to find existing caches. ##[debug]Cache service version: Identifies the API version (e.g., v2). You cannot browse the remote cache directly (unless

If your debug logs confirm that a corrupted cache is locked behind an immutable key, you must manually evict it to force your pipeline to rebuild from a clean slate. Method A: Deleting Caches via the GitHub UI Navigate to the main page of your GitHub repository. Click on the tab located under the repository name.

The command line arguments for the tool (e.g., compiler flags). Environment variables. The toolchain configuration. Share public link Use unique keys per job

When you use the actions/cache step (or the dedicated actions/cache/restore action), it initiates a restore operation. The debug logs will show it executing a specific sequence to locate a cache:

You haven’t changed any dependencies, yet the CI pipeline insists on downloading the entire internet on every single commit.

Now even if exact key misses, it restores the most recent linux-npm-* cache.