Update Yarn to v4.10.3 #1308
Triggered via pull request
September 18, 2025 17:37
renovate[bot]
Status
Success
Total duration
1m 47s
Artifacts
–
ci.yaml
on: pull_request
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
38s
Run publish action
0s
Annotations
48 warnings and 1 notice
|
Test on Node.js v22.x and jest v28
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>0WEPMaAAAAAABh5GcRloqTYGIz2++Do3FQ0hJMzBFREdFMDQwOQBFZGdl
|
|
Test on Node.js v22.x and jest v28
Cache not found
|
|
Test on Node.js v22.x and jest v28
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v22.x and jest v27
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>0VUPMaAAAAADdASXP0bBUR4lis0tTqeHyQkwyQUEyMDMwMTA4MDA1AEVkZ2U=
|
|
Test on Node.js v22.x and jest v27
Cache not found
|
|
Test on Node.js v22.x and jest v27
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v23.x and jest v28
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>0WUPMaAAAAABZ4JI76KbxRakrQUTeq3PuQ0hJMzBFREdFMDMwNwBFZGdl
|
|
Test on Node.js v23.x and jest v28
Cache not found
|
|
Test on Node.js v23.x and jest v28
Failed to restore: Cache service responded with 400
|
|
Test on macOS-latest using Node.js LTS
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>0XUPMaAAAAAA5+ok7rWGUSpccfLkgY1oUU04xRURHRTE1MTcARWRnZQ==
|
|
Test on macOS-latest using Node.js LTS
Cache not found
|
|
Test on macOS-latest using Node.js LTS
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v20.x and jest v27
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>0WEPMaAAAAACsthgswxyIRb3yoKBpMiF7Q0hJMzBFREdFMDQwNgBFZGdl
|
|
Test on Node.js v20.x and jest v27
Cache not found
|
|
Test on Node.js v20.x and jest v27
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v18.x and jest v28
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>0W0PMaAAAAAARzp8sQcCmQoQArk8wsDhmRE0yRURHRTAxMTIARWRnZQ==
|
|
Test on Node.js v18.x and jest v28
Cache not found
|
|
Test on Node.js v18.x and jest v28
Failed to restore: Cache service responded with 400
|
|
Test on ubuntu-latest using Node.js LTS
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>0WUPMaAAAAADiWgqC/9KESYiOQj9iZRz3RE0yRURHRTA4MjIARWRnZQ==
|
|
Test on ubuntu-latest using Node.js LTS
Cache not found
|
|
Test on ubuntu-latest using Node.js LTS
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v20.x and jest v29
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>0V0PMaAAAAAD+uS9AUPXeR6yM745qzVTIQkwyQUEyMDMwMTA5MDUzAEVkZ2U=
|
|
Test on Node.js v20.x and jest v29
Cache not found
|
|
Test on Node.js v20.x and jest v29
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v23.x and jest v27
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>0WUPMaAAAAADjy1zYONLkTLXo0+YptaPkQkwyQUEyMDMwMTA4MDE3AEVkZ2U=
|
|
Test on Node.js v23.x and jest v27
Cache not found
|
|
Test on Node.js v23.x and jest v27
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v18.x and jest v27
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>0WkPMaAAAAAAOx7B2gWfaQILkKSLrjcYXQlkzRURHRTA0MDkARWRnZQ==
|
|
Test on Node.js v18.x and jest v27
Cache not found
|
|
Test on Node.js v18.x and jest v27
Failed to restore: Cache service responded with 400
|
|
Run ESLint & TypeScript compiler
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>0VkPMaAAAAACHBRx1fF10RJQrZaxd7WHMQkwyQUEyMDMwMTA5MDUzAEVkZ2U=
|
|
Run ESLint & TypeScript compiler
Cache not found
|
|
Run ESLint & TypeScript compiler
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v20.x and jest v28
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>0VUPMaAAAAAAbihxc+SzpSrGQg1xAWjHEQkwyQUEyMDMwMTA5MDUxAEVkZ2U=
|
|
Test on Node.js v20.x and jest v28
Cache not found
|
|
Test on Node.js v20.x and jest v28
Failed to restore: Cache service responded with 400
|
|
Test on windows-latest using Node.js LTS
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>0a0PMaAAAAAC8NGYqUidnQaLLN2GKmlVVQkwyQUEyMDMwMTA4MDMxAEVkZ2U=
|
|
Test on windows-latest using Node.js LTS
Cache not found
|
|
Test on windows-latest using Node.js LTS
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v18.x and jest v29
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>0WkPMaAAAAACCPQwdcaNKTKal2EG0QbQtQ0hJMzBFREdFMDExOQBFZGdl
|
|
Test on Node.js v18.x and jest v29
Cache not found
|
|
Test on Node.js v18.x and jest v29
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v22.x and jest v29
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>0WUPMaAAAAADSdZT9jBWPTb0DUuA5PwD1QlkzRURHRTA0MDgARWRnZQ==
|
|
Test on Node.js v22.x and jest v29
Cache not found
|
|
Test on Node.js v22.x and jest v29
Failed to restore: Cache service responded with 400
|
|
Test on Node.js v23.x and jest v29
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>0W0PMaAAAAACrPYkCTY/GT73lC/JtCPODRE0yRURHRTA0MTAARWRnZQ==
|
|
Test on Node.js v23.x and jest v29
Cache not found
|
|
Test on Node.js v23.x and jest v29
Failed to restore: Cache service responded with 400
|
|
Test on windows-latest using Node.js LTS
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
|