Lock file maintenance (#815) #1302
renovate[bot]ci.yaml
on: push
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
29s
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>0r2i+aAAAAADd2VAdFlPGT67GDtW/mdD2QkwyQUEyMDMwMTA4MDUxAEVkZ2U=
|
|
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>0rWi+aAAAAADEIDN2v5YZQYAa8wHeakHnQkwyQUEyMDMwMTA1MDI3AEVkZ2U=
|
|
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 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>0r2i+aAAAAAAB4jsG2ajJRZZWd5zupDn0Q0hJMzBFREdFMDIxNQBFZGdl
|
|
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>0sWi+aAAAAAAL5cYY8Q06Q5PzN5WNhdgCQ0hJMzBFREdFMDMxMABFZGdl
|
|
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 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>0sWi+aAAAAABIFOfIAK+OQLeAeZDhqOIcQ0hJMzBFREdFMDExNgBFZGdl
|
|
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>0rmi+aAAAAAAr4q326aoNTqSixf9JlM8uQ0hJMzBFREdFMDMxOABFZGdl
|
|
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 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>0sGi+aAAAAACwU5Yvhhc1RZu0310NyXWcRE0yRURHRTA5MDkARWRnZQ==
|
|
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 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>0sGi+aAAAAACVbn4OUqlMRo5zcCcU/tKDQlkzRURHRTAxMjEARWRnZQ==
|
|
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 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>0r2i+aAAAAABWaLzZgZuXS5fgIG1GspThQ0hJMzBFREdFMDIwOQBFZGdl
|
|
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>0s2i+aAAAAAAxe8PZ5H9rTq82mGekBEauREVOMzAxMDAwMTA2MDMxAEVkZ2U=
|
|
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 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>0tGi+aAAAAADMyrScgW7WQpypLjUozvZkUEhYMzFFREdFMDYwOABFZGdl
|
|
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 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>0s2i+aAAAAAB16VrkJ75VQ4KrA4znEFQKREVOMzAxMDAwMTAxMDM5AEVkZ2U=
|
|
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>0t2i+aAAAAABZKaHo4C/WSIxVycu9whlYQkwyQUEyMDMwMTA4MDI3AEVkZ2U=
|
|
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 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>0tGi+aAAAAAC+cb4VErBuT51uf27ADR5hUEhYMzFFREdFMDUxMQBFZGdl
|
|
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 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>0vWi+aAAAAAA3k434lA0IRZkjjRoJp4DXUEFPRURHRTA2MTAARWRnZQ==
|
|
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 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>0xmi+aAAAAAAxiG2NNbJoTbgGTKSYKJ01REVOMzAxMDAwMTA4MDI1AEVkZ2U=
|
|
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
|
|
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>0Amm+aAAAAAD7VFgvOZk4QYtQYTl81ssdQlkzRURHRTA0MTcARWRnZQ==
|
|
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
|