3 ms·

I take the above back. TanStack messed this up in the way they explicitly cache. This is run from the affected workflow: https://github.com/TanStack/config/blob

by d3ng 5mo ago

I take the above back. TanStack messed this up in the way they explicitly cache. This is run from the affected workflow: https://github.com/TanStack/config/blob/main/.github/setup/action.yml#L22-L23 https://github.com/TanStack/config/blob/main/.github/setup/a... The restore-key looks too wide and this still looks like an issue. This wide caching may also cause issue if they ever upgrade major nodejs version independently of OS, for example.

user34283 5mo ago
On GitLab even if you set the same cache key it will not cross between unprotected and protected runs. GitLab just adds a -protected suffix to the cache key. It seems baffling that GitHub does not do this trivial separation, if I understand it correctly.