Vipul
@kevinlul Please keep the step debugging on and provide the logs if it reoccurs anytime soon.
@Sytten I don't think anything is being planned in this direction for GitHub.com right now as maintaining regions manually so that cache can work effectively will be very difficult in...
@metaclips Will it be possible for you to rerun this scenario? I'll take a look. The logs you mentioned have expired.
I did get to check this by cloning the repo above. Looks like we store the key in the environment during the restore step which is reused in the save...
@ManuLpz4 a cache created on the default branch would be accessible from any pull request. What problems were you facing? Are you using a different branch other than the default...
@bchen1029 Please fix the failing checks. Updating the branch and then running `npm run build` should fix it ig.
@mondeja Unless the windows-latest test is fixed, I won't be able to merge this. Please see if you can fix it.
@mondeja Yes, please regenerate dist/ as that will be required for merging. When we create a new release, users using actions/cache@v3 will be pointed to the new release with this...
Hmm for dist/ files there shouldn't be conflicts. I'll take a look.
@mondeja What version of npm are you using ? I checkout out your branch and regenerated dist/ . There were some changes - ``` @vsvipul ➜ /workspaces/cache (fix-345) $ npm...