Skip to content
This repository was archived by the owner on Oct 14, 2025. It is now read-only.

[Snyk] Security upgrade @actions/cache from 3.2.213 to 4.0.0 #22

[Snyk] Security upgrade @actions/cache from 3.2.213 to 4.0.0

[Snyk] Security upgrade @actions/cache from 3.2.213 to 4.0.0 #22

Triggered via pull request September 12, 2025 00:49
Status Failure
Total duration 1m 54s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

e2e-cache.yml

on: pull_request
Matrix: gradle-save
Matrix: maven-save
Matrix: sbt-save
Matrix: gradle-restore
Matrix: maven-restore
Matrix: sbt-restore
Fit to window
Zoom out
Zoom in

Annotations

11 errors, 28 warnings, and 4 notices
sbt-save (ubuntu-latest)
Process completed with exit code 127.
gradle-save (ubuntu-latest)
Process completed with exit code 1.
gradle-save (windows-latest)
Process completed with exit code 1.
sbt-save (macos-latest)
Process completed with exit code 127.
maven-restore (macos-latest)
Process completed with exit code 1.
maven-restore (macos-latest)
The ~/.m2/repository directory does not exist unexpectedly
maven-restore (ubuntu-latest)
Process completed with exit code 1.
maven-restore (ubuntu-latest)
The ~/.m2/repository directory does not exist unexpectedly
maven-restore (windows-latest)
Process completed with exit code 1.
maven-restore (windows-latest)
The ~/.m2/repository directory does not exist unexpectedly
gradle-save (macos-latest)
Process completed with exit code 1.
sbt-save (ubuntu-latest)
Failed to report failure to api.blacksmith.sh
sbt-save (ubuntu-latest)
Failed to restore: Cache service responded with 401
gradle-save (ubuntu-latest)
Failed to report failure to api.blacksmith.sh
gradle-save (ubuntu-latest)
Failed to restore: Cache service responded with 401
gradle-save (windows-latest)
Failed to report failure to api.blacksmith.sh
gradle-save (windows-latest)
Failed to restore: Cache service responded with 401
maven-save (ubuntu-latest)
Failed to save: reserveCache failed: Invalid value "undefined" for header "x-github-repo-name"
maven-save (ubuntu-latest)
Failed to report failure to api.blacksmith.sh
maven-save (ubuntu-latest)
Failed to restore: Cache service responded with 401
maven-save (macos-latest)
Failed to save: reserveCache failed: Invalid value "undefined" for header "x-github-repo-name"
maven-save (macos-latest)
Failed to report failure to api.blacksmith.sh
maven-save (macos-latest)
Failed to restore: Cache service responded with 401
sbt-save (macos-latest)
Failed to report failure to api.blacksmith.sh
sbt-save (macos-latest)
Failed to restore: Cache service responded with 401
maven-save (windows-latest)
Failed to save: reserveCache failed: Invalid value "undefined" for header "x-github-repo-name"
maven-save (windows-latest)
Failed to report failure to api.blacksmith.sh
maven-save (windows-latest)
Failed to restore: Cache service responded with 401
sbt-save (windows-latest)
Failed to save: reserveCache failed: Invalid value "undefined" for header "x-github-repo-name"
sbt-save (windows-latest)
Failed to report failure to api.blacksmith.sh
sbt-save (windows-latest)
Failed to restore: Cache service responded with 401
maven-restore (macos-latest)
Failed to report failure to api.blacksmith.sh
maven-restore (macos-latest)
Failed to restore: Cache service responded with 401
maven-restore (ubuntu-latest)
Failed to report failure to api.blacksmith.sh
maven-restore (ubuntu-latest)
Failed to restore: Cache service responded with 401
maven-restore (windows-latest)
Failed to report failure to api.blacksmith.sh
maven-restore (windows-latest)
Failed to restore: Cache service responded with 401
gradle-save (macos-latest)
Failed to report failure to api.blacksmith.sh
gradle-save (macos-latest)
Failed to restore: Cache service responded with 401
gradle-save (windows-latest)
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
maven-save (windows-latest)
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
sbt-save (windows-latest)
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
maven-restore (windows-latest)
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