You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @geemus 👋,
Thank you for sharing the details!
I tried to replicate the error using the provided code snippet, but was unable to do so. By default, the actions/setup-node action looks for a dependency lock file in your repository's root. If this file is not found, the setup step will fail. You can find more information in this related document.
As I couldn't reproduce your issue, it would be really helpful if you could share a link to a minimal reproduction of the problem for further investigation. Thank you in advance:)
Thanks for checking on this. I changed some things to ensure there is a lock file present, but it doesn't seem to have made a difference. FWIW we run the same jobs on mac and ubuntu and they worked fine both before and after (and everything but the cache save afterward seems to work on windows). I also tried to setup a minimal reproduction case, but so far I haven't figured out how to get it to fail (it seems to work just fine, probably similar to what you saw).
Hello there👋,
Any luck creating a reproducible scenario? This would greatly help us in diagnosing and fixing the issue. Thanks in advance for your cooperation:)
Description:
Post job cleanup fails with permission issues:
Action version:
actions/setup-node@v4
Platform:
Runner type:
Tools version:
node 20.10.0
npm (? I didn't specify, so the default I suppose)
Repro steps:
Here are what I think would be the relevant bits from our setup:
I'll note that we just have a
package.json
and no lock at present in case that is relevant.Expected behavior:
I expected the caching to "just work" with this setup, as it does with the same invocation on mac/ubuntu.
Actual behavior:
Setup node and the rest of the action work fine, but the cleanup/caching fails (so there is never a cache to be used).
The text was updated successfully, but these errors were encountered: