Debug-action-cache !new! Jun 2026

Use --action_env to limit environmental variables.

: Use the mxschmitt/action-tmate action to pause your workflow and SSH into the runner. This allows you to manually check if the files were actually restored to the directory you expected.

Is USER or HOSTNAME being sucked into the action? debug-action-cache

Demystifying debug-action-cache : A Complete Guide to Troubleshooting Action Cache Issues

Compilers or code generators that embed the current time into the binary. Use --action_env to limit environmental variables

Once set, re-run your workflow. You will see logs prefixed with [debug] inside the cache step.

Mastering debug-action-cache : How to Troubleshoot and Optimize GitHub Actions Caching Is USER or HOSTNAME being sucked into the action

: Check the hashFiles output in logs to ensure your lockfiles (e.g., package-lock.json ) are being picked up correctly.

You likely arrived at the need for debug-action-cache because your pipeline is exhibiting one of the following symptoms:

curl -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer YOUR_GITHUB_TOKEN" \ "https://api.github.com/repos/OWNER/REPO/actions/caches"

: Set to true to enable verbose individual step logs. Add Debugging Variables to Your Workflow