From fc524a0565d5c96d9fdd812703c2a2929f4f6e20 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 22 Oct 2024 12:23:13 -0400 Subject: [PATCH] chore(deps): bump actions/cache from 4.1.1 to 4.1.2 (#3364) Bumps [actions/cache](https://github.com/actions/cache) from 4.1.1 to 4.1.2. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](https://github.com/actions/cache/compare/3624ceb22c1c5a301c8db4169662070a689d9ea8...6849a6489940f00c2f30c0fb92c6274307ccb58a) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- .github/workflows/benchmark-testing.yaml | 2 +- .github/workflows/validations.yaml | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/benchmark-testing.yaml b/.github/workflows/benchmark-testing.yaml index f704868f0..5225b3c28 100644 --- a/.github/workflows/benchmark-testing.yaml +++ b/.github/workflows/benchmark-testing.yaml @@ -23,7 +23,7 @@ jobs: uses: ./.github/actions/bootstrap - name: Restore base benchmark result - uses: actions/cache@3624ceb22c1c5a301c8db4169662070a689d9ea8 #v4.1.1 + uses: actions/cache@6849a6489940f00c2f30c0fb92c6274307ccb58a #v4.1.2 with: path: test/results/benchmark-main.txt # use base sha for PR or new commit hash for main push in benchmark result key diff --git a/.github/workflows/validations.yaml b/.github/workflows/validations.yaml index ab4f7cf4c..095c16ab6 100644 --- a/.github/workflows/validations.yaml +++ b/.github/workflows/validations.yaml @@ -78,7 +78,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@3624ceb22c1c5a301c8db4169662070a689d9ea8 #v4.1.1 + uses: actions/cache/save@6849a6489940f00c2f30c0fb92c6274307ccb58a #v4.1.2 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 @@ -104,7 +104,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@3624ceb22c1c5a301c8db4169662070a689d9ea8 #v4.1.1 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a #v4.1.2 with: path: | snapshot @@ -152,7 +152,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@3624ceb22c1c5a301c8db4169662070a689d9ea8 #v4.1.1 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a #v4.1.2 with: path: | snapshot @@ -187,7 +187,7 @@ jobs: - name: Download snapshot build id: snapshot-cache - uses: actions/cache/restore@3624ceb22c1c5a301c8db4169662070a689d9ea8 #v4.1.1 + uses: actions/cache/restore@6849a6489940f00c2f30c0fb92c6274307ccb58a #v4.1.2 with: path: | snapshot