diff --git a/.github/workflows/validations.yaml b/.github/workflows/validations.yaml index f9eb6c3d4..d63466b20 100644 --- a/.github/workflows/validations.yaml +++ b/.github/workflows/validations.yaml @@ -90,7 +90,7 @@ jobs: # why not use actions/upload-artifact? It is very slow (3 minutes to upload ~600MB of data, vs 10 seconds with this approach). # see https://github.com/actions/upload-artifact/issues/199 for more info - name: Upload snapshot artifacts - uses: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830 #v4.3.0 + uses: actions/cache/save@a7833574556fa59680c1b7cb190c1735db73ebf0 #v5.0.0 with: # we need to preserve the snapshot data itself as well as the task data that confirms if the # snapshot build is stale or not. Otherwise the downstream jobs will attempt to rebuild the snapshot @@ -118,7 +118,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 #v4.3.0 + uses: actions/cache/restore@a7833574556fa59680c1b7cb190c1735db73ebf0 #v5.0.0 with: path: | snapshot @@ -175,7 +175,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 #v4.3.0 + uses: actions/cache/restore@a7833574556fa59680c1b7cb190c1735db73ebf0 #v5.0.0 with: path: | snapshot @@ -225,7 +225,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 #v4.3.0 + uses: actions/cache/restore@a7833574556fa59680c1b7cb190c1735db73ebf0 #v5.0.0 with: path: | snapshot @@ -262,7 +262,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 #v4.3.0 + uses: actions/cache/restore@a7833574556fa59680c1b7cb190c1735db73ebf0 #v5.0.0 with: path: | snapshot