Skip to content

[Snyk] Upgrade @types/node from 20.17.14 to 20.19.9 #24

[Snyk] Upgrade @types/node from 20.17.14 to 20.19.9

[Snyk] Upgrade @types/node from 20.17.14 to 20.19.9 #24

Triggered via pull request August 27, 2025 15:30
Status Failure
Total duration 14m 4s
Artifacts

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

10 errors, 17 warnings, and 4 notices
gradle-save (ubuntu-latest)
Process completed with exit code 1.
gradle-save (macos-13)
Process completed with exit code 1.
sbt-save (ubuntu-latest)
Process completed with exit code 127.
gradle-save (windows-latest)
Process completed with exit code 1.
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
maven-restore (macos-13)
Process completed with exit code 1.
maven-restore (macos-13)
The ~/.m2/repository directory does not exist unexpectedly
gradle-save (ubuntu-latest)
Failed to restore: Cache service responded with 400
maven-save (macos-13)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0KCWvaAAAAAAB8znXZjU/RZR7WTJSSzs3QlkzRURHRTAxMTgARWRnZQ==
maven-save (macos-13)
Failed to restore: Cache service responded with 400
maven-save (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0MSWvaAAAAAATuhOtzY6sQaQ86ms0aKAyQkwyQUEyMDMwMTA4MDA5AEVkZ2U=
maven-save (ubuntu-latest)
Failed to restore: Cache service responded with 400
gradle-save (macos-13)
Failed to restore: Cache service responded with 400
sbt-save (ubuntu-latest)
Failed to restore: Cache service responded with 400
sbt-save (windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0VyWvaAAAAAAU4+C6ejnfRpzGhPGpH+2bQkwyQUEyMDMwMTA4MDExAEVkZ2U=
sbt-save (windows-latest)
Failed to restore: Cache service responded with 400
gradle-save (windows-latest)
Failed to restore: Cache service responded with 400
maven-save (windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YSWvaAAAAADHcouGdp2rTIc8A/lZh3wKRE0yRURHRTEwMDgARWRnZQ==
maven-save (windows-latest)
Failed to restore: Cache service responded with 400
sbt-save (macos-13)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0giWvaAAAAADExGi1GfpVT5W8gERU2NiuUEFPRURHRTA2MTAARWRnZQ==
sbt-save (macos-13)
Failed to restore: Cache service responded with 400
maven-restore (ubuntu-latest)
Failed to restore: Cache service responded with 400
maven-restore (windows-latest)
Failed to restore: Cache service responded with 400
maven-restore (macos-13)
Failed to restore: Cache service responded with 400
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
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
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