Conversation
With this change, caches become immutable by appending the workflow run_id, which makes the actual key unique (appart from re-run) The cache restore works because the primaryKey is a prefix anyway: https://github.com/actions/toolkit/blob/1b1e81526b802d1d641911393281c2fb45ed5f11/packages/cache/src/cache.ts#L67 This follows recommendations from https://github.com/actions/cache/blob/main/tips-and-workarounds.md#update-a-cache Unused caches are removed after 7 days by github: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy This avoids users having to define unneeded permission `actions: write`
/ |
Description:
With this change, caches become immutable by appending the workflow run_id, which makes the actual key unique (appart from re-run)
The cache restore works because the primaryKey is a prefix anyway: https://github.com/actions/toolkit/blob/1b1e81526b802d1d641911393281c2fb45ed5f11/packages/cache/src/cache.ts#L67
This follows recommendations from https://github.com/actions/cache/blob/main/tips-and-workarounds.md#update-a-cache
Unused caches are removed after 7 days by github:
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy
This avoids users having to define unneeded permission
actions: writeThe problem with deleting a cache entry is that it requires to give
actions: writepermissions, which means the workflow has all these permissions and this is way too much, and not acceptable for a lot of projects.CI results available in https://github.com/ericLemanissier/stale/pull/71/checks
Related issue:
fixes #1159
fixes #1133
fixes #1131
Check list: