You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ jobs:
95
95
96
96
- name: Cache Primes
97
97
id: cache-primes
98
-
uses: actions/cache@v3
98
+
uses: actions/cache@v4
99
99
with:
100
100
path: prime-numbers
101
101
key: ${{ runner.os }}-primes
@@ -126,7 +126,7 @@ jobs:
126
126
127
127
- name: Restore cached Primes
128
128
id: cache-primes-restore
129
-
uses: actions/cache/restore@v3
129
+
uses: actions/cache/restore@v4
130
130
with:
131
131
path: |
132
132
path/to/dependencies
@@ -137,7 +137,7 @@ jobs:
137
137
.
138
138
- name: Save Primes
139
139
id: cache-primes-save
140
-
uses: actions/cache/save@v3
140
+
uses: actions/cache/save@v4
141
141
with:
142
142
path: |
143
143
path/to/dependencies
@@ -191,7 +191,7 @@ A cache key can include any of the contexts, functions, literals, and operators
191
191
For example, using the [`hashFiles`](https://docs.github.com/en/actions/learn-github-actions/expressions#hashfiles) function allows you to create a new cache when dependencies change.
192
192
193
193
```yaml
194
-
- uses: actions/cache@v3
194
+
- uses: actions/cache@v4
195
195
with:
196
196
path: |
197
197
path/to/dependencies
@@ -209,7 +209,7 @@ Additionally, you can use arbitrary command output in a cache key, such as a dat
0 commit comments