Bump com.gradle.develocity from 4.1.1 to 4.2 #1784
Triggered via pull request
September 17, 2025 00:16
dependabot[bot]
Status
Success
Total duration
5m 38s
Artifacts
–
Annotations
2 errors, 8 warnings, and 2 notices
|
build (17, windows-latest, true)
Process completed with exit code 1.
|
|
build (21, windows-latest, true)
Process completed with exit code 1.
|
|
android-tests (30)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
android-tests (30)
Failed to restore gradle-home-v1|Linux|android-tests[daac2a1c3688d65eb139c0a53e71922a]-82342ddc35f83a1b52ecf3180036c8f6f8bf1061: Error: Cache service responded with 400
|
|
android-tests (26)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
android-tests (26)
Failed to restore gradle-home-v1|Linux|android-tests[3b1101b3a16bb09f415568f97d043434]-82342ddc35f83a1b52ecf3180036c8f6f8bf1061: Error: Cache service responded with 400
|
|
android-tests (34)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
android-tests (34)
Failed to restore gradle-home-v1|Linux|android-tests[d1bb53cfd595ebf8ab3488de6934995e]-82342ddc35f83a1b52ecf3180036c8f6f8bf1061: Error: Cache service responded with 400
|
|
android-tests (21)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
|
|
android-tests (21)
Failed to restore gradle-home-v1|Linux|android-tests[6d9e38995fae1c7cd6b589df2258f241]-82342ddc35f83a1b52ecf3180036c8f6f8bf1061: Error: Cache service responded with 400
|
|
build (17, windows-latest, true)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
build (21, windows-latest, true)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|