Compare commits

...

5 Commits

Author SHA1 Message Date
Rik Huijzer
d32eadb01c
Merge 62a3e42441 into 704facf57e 2023-09-08 16:41:32 +10:00
Bethany
704facf57e
Merge pull request #1236 from actions/bethanyj28/bump-version
Bump action version to 3.3.2
2023-09-07 16:31:19 -04:00
bethanyj28
17e2888746 Add to RELEASES.md 2023-09-06 14:41:49 -04:00
bethanyj28
667d8fdfa2 bump action version to 3.3.2 2023-09-06 14:15:33 -04:00
rikhuijzer
62a3e42441 Mention empty possibility for outputs.cache-hit 2023-04-24 09:20:22 +02:00
5 changed files with 9 additions and 5 deletions

View File

@ -60,7 +60,7 @@ If you are using a `self-hosted` Windows runner, `GNU tar` and `zstd` are requir
### Outputs
* `cache-hit` - A boolean value to indicate an exact match was found for the key.
* `cache-hit` - A boolean value to indicate an exact match was found for the key, or empty (not set) if no cache was restored.
> **Note** `cache-hit` will only be set to `true` when a cache hit occurs for the exact `key` match. For a partial key match via `restore-keys` or a cache miss, it will be set to `false`.

View File

@ -107,3 +107,7 @@
### 3.3.1
- Reduced segment size to 128MB and segment timeout to 10 minutes to fail fast in case the cache download is stuck.
### 3.3.2
- Fixes bug with Azure SDK causing blob downloads to get stuck.

4
package-lock.json generated
View File

@ -1,12 +1,12 @@
{
"name": "cache",
"version": "3.3.1",
"version": "3.3.2",
"lockfileVersion": 2,
"requires": true,
"packages": {
"": {
"name": "cache",
"version": "3.3.1",
"version": "3.3.2",
"license": "MIT",
"dependencies": {
"@actions/cache": "^3.2.2",

View File

@ -1,6 +1,6 @@
{
"name": "cache",
"version": "3.3.1",
"version": "3.3.2",
"private": true,
"description": "Cache dependencies and build outputs",
"main": "dist/restore/index.js",

View File

@ -14,7 +14,7 @@ The restore action restores a cache. It works similarly to the `cache` action ex
### Outputs
* `cache-hit` - A boolean value to indicate an exact match was found for the key.
* `cache-hit` - A boolean value to indicate an exact match was found for the key, or empty (not set) if no cache was restored.
* `cache-primary-key` - Cache primary key passed in the input to use in subsequent steps of the workflow.
* `cache-matched-key` - Key of the cache that was restored, it could either be the primary key on cache-hit or a partial/complete match of one of the restore keys.