Fix Gradle cache save races when restore hits a fallback key.

Save always uses the job scope key; do not reuse cache-primary-key from a partial restore (e.g. Android saving build-jar).

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-09-14 16:11:33 +03:00
Unverified
parent 3416bc2b0e
commit 7d7e78c534
3 changed files with 12 additions and 12 deletions
@@ -2,8 +2,8 @@ name: Save Gradle build directories
description: Save project .gradle/, build/ trees after a Gradle build
inputs:
primary-key:
description: cache-primary-key from cache-gradle-build restore step
scope:
description: Same scope passed to cache-gradle-build (save always uses this job's key, not a restored fallback key)
required: true
runs:
@@ -12,7 +12,7 @@ runs:
- uses: actions/cache/save@v5
continue-on-error: true
with:
key: ${{ inputs.primary-key }}
key: gradle-build-${{ runner.os }}-${{ runner.arch }}-v2-${{ inputs.scope }}-${{ hashFiles('gradle/libs.versions.toml', 'settings.gradle.kts', 'gradle.properties', 'build.gradle.kts', 'app/desktop/build.gradle.kts', 'app/desktop/proguard-rules.pro', 'app/shared/build.gradle.kts', 'app/android/build.gradle.kts', 'utils/shared/build.gradle.kts', 'utils/android/build.gradle.kts') }}
path: |
.gradle
build