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
@jsnoble had added the yarn cache to some of his node setup actions as did I, but I thought they weren't working. I did just find some evidence of this working on the standard-assets project:
Maybe I just don't understand when the cache gets used. I had assumed, perhaps erroneously, that they were not working because of messages like this on the node setup action
Run actions/setup-node@v3
Found in cache @ /opt/hostedtoolcache/node/14.21.3/x64
Environment details
/usr/local/bin/yarn --version
1.18.0
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v4
yarn cache is not found
Oh, I'm confusing the tool cache with the yarn cache ... this message is about the toolcache, which is where node setup gets it's node release for a specific version
Found in cache @ /opt/hostedtoolcache/node/18.16.0/x64
@jsnoble had added the yarn cache to some of his node setup actions as did I, but I thought they weren't working. I did just find some evidence of this working on the
standard-assets
project:Obviously this is a feature we want, but we want to make sure we understand it well enough to use it properly, we want it to work.
The text was updated successfully, but these errors were encountered: