Compare commits

..

No commits in common. "9365bab5e5c65fe74808a7ec017db5941eaa213b" and "40b3745dc1bc833cbb3c4fe0d73bd74a5e3a89f2" have entirely different histories.

2 changed files with 2 additions and 2 deletions

View File

@ -76,7 +76,7 @@ If you are using a `self-hosted` Windows runner, `GNU tar` and `zstd` are requir
* `enableCrossOsArchive` - An optional boolean when enabled, allows Windows runners to save or restore caches that can be restored or saved respectively on other platforms. Default: `false`
* `fail-on-cache-miss` - Fail the workflow if cache entry is not found. Default: `false`
* `lookup-only` - If true, only checks if cache entry exists and skips download. Does not change save cache behavior. Default: `false`
* `save-on-success` - If true, then the cache is written in the post action on success, or (if false) the cache will only be restored if available. Default: `true`
* `save-on-success` - If true, then the cache is written in the post action on success, or (if false) the cache will only be restored if available.
#### Environment Variables

View File

@ -36,7 +36,7 @@ inputs:
required: false
deprecationMessage: |
save-always does not work as intended and will be removed in a future release.
If you only want to control whether a new cache will be written use `save-on-success` instead.
If you only want to control whether a new cache will be written use `save-always` instead.
Otherwise a separate `actions/cache/restore` step should be used instead.
See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
outputs: