Update dependency lint-staged to ~16.2.0 #1330
renovate[bot]ci.yaml
on: pull_request
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
38s
Run publish action
Annotations
48 warnings
|
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>0HxvqaAAAAAA9/Rz3rbzyR7Wn8XComkwVQ0hJMzBFREdFMDQyMABFZGdl
|
|
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 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>0IhvqaAAAAAArCEBMzjKfRrUV6QfCylTNQ0hJMzBFREdFMDQxMABFZGdl
|
|
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 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>0HxvqaAAAAACGm8kW59p6QZoh4ZeVpLiORE0yRURHRTA4MjEARWRnZQ==
|
|
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
|
|
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>0JBvqaAAAAABFKg29IsotTZ3wE1HfdblSUEFPRURHRTA1MTYARWRnZQ==
|
|
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>0IxvqaAAAAABdfE7JiqKeQYROCdy5kTVBUEhMMzBFREdFMDIxMQBFZGdl
|
|
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 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>0IhvqaAAAAAA5ZrBadSi+TKuG4znFlA8XQ0hJMzBFREdFMDIxOABFZGdl
|
|
Test on Node.js v22.x and jest v28
Cache not found
|
|
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>0IhvqaAAAAAAYQsaIdXGLSo3MQpU6viXcUEhMMzBFREdFMDIyMQBFZGdl
|
|
Test on Node.js v22.x and jest v28
Failed to restore: Cache service responded with 400
|
|
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 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>0JBvqaAAAAACtr+fadv3uQqv/DMUG6eR8UEhMMzBFREdFMDExOABFZGdl
|
|
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 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>0IhvqaAAAAABWp+9HCea4T5IxOfKwGBKXQ0hJMzBFREdFMDQxMABFZGdl
|
|
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>0IhvqaAAAAADphJFQQfF3TrA1myL9rCjOUEhMMzBFREdFMDQyMABFZGdl
|
|
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>0IxvqaAAAAACpi/wvouIMRq735/aq1ekOQ0hJMzBFREdFMDMxMgBFZGdl
|
|
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>0JRvqaAAAAACvGG0c7DDXS4QwEvO1ueEFU04xRURHRTE2MDgARWRnZQ==
|
|
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 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>0IxvqaAAAAAC2EGUmtqZJSpa3DA+gA789Q0hJMzBFREdFMDIyMABFZGdl
|
|
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 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>0JRvqaAAAAAAWz6GKZjYNQqM3sqTsqX9EREVOMzAxMDAwMTA3MDQ5AEVkZ2U=
|
|
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 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>0JRvqaAAAAABuiAa0RUyWTL7WTXCqpofWUEhYMzFFREdFMDUxMgBFZGdl
|
|
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 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>0ThvqaAAAAAC5qPD4VwcMTbwfkbsHX9WxREVOMzAxMDAwMTA0MDIxAEVkZ2U=
|
|
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
|