: Set to true to enable verbose individual step logs. Add Debugging Variables to Your Workflow
View cache usage in your Action workflows - GitHub Changelog
A feature branch restores a cache from main that contains binaries incompatible with the branch’s code. Debugging: Enable step debug – you’ll see restore-keys matched Linux-node- which pulled a cache from main . Fix: Use branch-specific keys: key: $ runner.os -node-$ github.ref_name -$ hashFiles(...) . debug-action-cache
: Check the hashFiles output in logs to ensure your lockfiles (e.g., package-lock.json ) are being picked up correctly.
Helps you test key logic without pushing commits. : Set to true to enable verbose individual step logs
If you find a corrupted cache, you cannot edit it. You must delete it. GitHub does not have a UI for deleting individual caches (as of 2025), but you can use the gh CLI or the delete-cache action.
step before your cache step to verify the files being hashed exist and have the expected content. Immutable Keys Fix: Use branch-specific keys: key: $ runner
Once you have basic visibility, you can move to advanced diagnostics.
If the cache is restoring files but they aren't where you expect them, use action-tmate to log into the runner via SSH while the job is active.
"id": 123456, "key": "Linux-node-abc123", "size_in_bytes": 245000000, "created_at": "2025-04-01T10:00:00Z", "last_accessed_at": "2025-04-02T10:00:00Z"