Update Yarn to v4.10.3 #1309
Triggered via pull request
September 18, 2025 20:52
renovate[bot]
Status
Success
Total duration
1m 33s
Artifacts
–
ci.yaml
on: pull_request
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
41s
Run publish action
0s
Annotations
48 warnings and 1 notice
|
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>0JHHMaAAAAACMOfst/BKiRKMJ436l9cVjU04xRURHRTIxMTMARWRnZQ==
|
|
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 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>0JXHMaAAAAADAATtR0d+ERa/ZozLJ0XptQkwyQUEyMDMwMTA5MDI3AEVkZ2U=
|
|
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
|
|
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>0KHHMaAAAAADYjLHPYujsTrQR4ypFzieZRE0yRURHRTA0MTEARWRnZQ==
|
|
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 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>0JXHMaAAAAAA2m+9pAwlXQL5KQ20jn0+CQkwyQUEyMDMwMTEwMDA5AEVkZ2U=
|
|
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 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>0JXHMaAAAAACWi3ap5tWGQ7V8+vjyF30PQkwyQUEyMDMwMTA4MDQ3AEVkZ2U=
|
|
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 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>0JXHMaAAAAAD2l+/mAi33RpY91M549aD8QkwyQUEyMDMwMTEwMDQ1AEVkZ2U=
|
|
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 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>0I3HMaAAAAAATx0EU4o3XQJetIe9KcMVvQkwyQUEyMDMwMTEwMDA1AEVkZ2U=
|
|
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
|
|
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>0JHHMaAAAAAChIXi7aJYBQ7dcHPO/+sO3RE0yRURHRTA1MTUARWRnZQ==
|
|
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 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>0JXHMaAAAAADCOoC7XLyWSoEdP1CDeBmOUEhYMzFFREdFMDIyMQBFZGdl
|
|
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 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>0KXHMaAAAAAA1VhG1xz8ES5/TzBPIuuEZQ0hJMzBFREdFMDIxOABFZGdl
|
|
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 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>0KHHMaAAAAABJs+xHGHznSLmdHS7TRMzzQlkzRURHRTAxMTcARWRnZQ==
|
|
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 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>0KXHMaAAAAABR1O/JSEyyR6+NSlgqXTofQ0hJMzBFREdFMDIwOABFZGdl
|
|
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 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>0KXHMaAAAAAC2QedJsQFyTK8XLuN/2JJjQlkzRURHRTA1MDkARWRnZQ==
|
|
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 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>0KXHMaAAAAAAxay1A3jZiR48MIwkCANccQ0hJMzBFREdFMDIwOABFZGdl
|
|
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 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>0KnHMaAAAAACLYnYR9mtEQ6D8oFr16vowRE0yRURHRTA0MTQARWRnZQ==
|
|
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 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>0PHHMaAAAAAAw7VMD/XOeRKdBjuALc48QQlkzRURHRTAyMTcARWRnZQ==
|
|
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 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
|