Update Yarn to v4.10.3 (#812) #1315
SimenBci.yaml
on: push
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
30s
Run publish action
22s
Annotations
51 warnings and 1 notice
|
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>033nSaAAAAAAA2PoMEVVQToZthHLZOI8qQ0hJMzBFREdFMDQxNwBFZGdl
|
|
Run ESLint & TypeScript compiler
Cache not found
|
|
Run ESLint & TypeScript compiler
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>04HnSaAAAAACVQZkWjdGESbbjUVU71QjKQ0hJMzBFREdFMDMwNwBFZGdl
|
|
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 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>04HnSaAAAAADclYBf0owdT42+4RzsEuzjQ0hJMzBFREdFMDQwOQBFZGdl
|
|
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 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>04HnSaAAAAADlq70W2asmRqev3A0GI9IlQkwyQUEyMDMwMTA4MDMzAEVkZ2U=
|
|
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 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>04nnSaAAAAAA7Fy3r7CiPTJNeOgvocVPYQkwyQUEyMDMwMTA5MDI5AEVkZ2U=
|
|
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 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>04HnSaAAAAABv3apI+kHLQZRxYRWp1hGrUEFPRURHRTA1MTMARWRnZQ==
|
|
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 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>04nnSaAAAAACYJY3NEjR5QYmhiBvMRKQVQlkzRURHRTA1MTcARWRnZQ==
|
|
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 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>04nnSaAAAAABJDUnOscTrRqbdNkapoNF4QlkzRURHRTAzMjAARWRnZQ==
|
|
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 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>04XnSaAAAAADuUEJvPeZ6Qo4xVZ79N12rQkwyQUEyMDMwMTA5MDI3AEVkZ2U=
|
|
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 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>04XnSaAAAAAASb7UmFWKMSJkYxyiezHrKQlkzRURHRTAzMDkARWRnZQ==
|
|
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>05HnSaAAAAABphIEuJwslTYiZKiwDWOgBQlkzRURHRTAyMDgARWRnZQ==
|
|
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 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>05HnSaAAAAAD72NM0v7C/Trql0gAbzackRE0yRURHRTEwMTEARWRnZQ==
|
|
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 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>08nnSaAAAAAAs0ytXkShgQa9HeBJUc8F0QkwyQUEyMDMwMTA4MDI3AEVkZ2U=
|
|
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 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>083nSaAAAAADVjJt3VdgrRJMLIC192EGRQ0hJMzBFREdFMDQxMQBFZGdl
|
|
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 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>06nnSaAAAAAAebtw9nWU7RKA1mmOzr2tkQkwyQUEyMDMwMTA4MDM3AEVkZ2U=
|
|
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 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>09XnSaAAAAAC7bCDBHt9GQrKJKe9RX8nNQ0hJMzBFREdFMDIwNwBFZGdl
|
|
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 publish action
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>0HXrSaAAAAACCvuMmCYFkT59iZuYR0elCQkwyQUEyMDMwMTA5MDQ1AEVkZ2U=
|
|
Run publish action
Cache not found
|
|
Run publish action
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
|