Open IanButterworth opened 10 months ago
Have you validated this is working? This failed CI run didn't seem to save the cache:
It appears to be a CI glitch. CI had stalled and I did a partial re-run only of the failed jobs, which might not be valid for the test setup here.
There's a macos runner stalling here now too
I've been meaning to test this on another repo with forced failure. I'll check before merge
Yeah this is broken (never worked) upstream. PR to fix it https://github.com/actions/cache/pull/1325
There's a staggering lack of review urgency on the upstream fix PR https://github.com/actions/cache/pull/1325
It makes me wonder if we should maintain a fork of actions/cache
Based upon this comment the change to actions/cache@v4
should be considered breaking here. I think we'll be merging #123 first which means this change will be non-breaking for the upcoming release (v2
).
actions/cache
are planning to remove the (non-working) save-always
option which I think makes the goal of this PR impossible.
https://github.com/actions/cache/issues/1315#issuecomment-2163822166
Marking as draft until (if/when) the blockers in https://github.com/actions/cache/issues/1315#issuecomment-2163822166 become unblocked.
Closes #79