Update docusaurus monorepo to v3.9.2 #1320
Triggered via pull request
September 26, 2025 18:41
renovate[bot]
Status
Success
Total duration
1m 37s
Artifacts
–
ci.yaml
on: pull_request
Matrix: test-node
Matrix: test-os
Run ESLint & TypeScript compiler
42s
Run publish action
Annotations
48 warnings and 1 notice
|
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>0c97WaAAAAADBFMAI/pmGR5UOfasWPH9hUEhMMzBFREdFMDQyMQBFZGdl
|
|
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 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>0dN7WaAAAAAB1medSfqqMTYjMALrbRVKeUEhMMzBFREdFMDIxMgBFZGdl
|
|
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 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>0dt7WaAAAAACPUAYR7AWwR4XqHO2zQFdGUEhMMzBFREdFMDExMQBFZGdl
|
|
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 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>0dd7WaAAAAAAz7vQzdg3TRL11mIl+j++bU04xRURHRTE5MTIARWRnZQ==
|
|
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 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>0dd7WaAAAAABygYWSw0Q+SqHy09s1giCBQ0hJMzBFREdFMDIwOQBFZGdl
|
|
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 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>0d97WaAAAAABceLugzVOSRo5V5sam78FjUEhMMzBFREdFMDExOQBFZGdl
|
|
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 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>0d97WaAAAAAAUXui6MIKMRYWGc7iEBUyTUEhYMzFFREdFMDUxOABFZGdl
|
|
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>0d97WaAAAAADzAzQXXTEzTL/tRFX+tLw0UEhYMzFFREdFMDUwOQBFZGdl
|
|
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>0dd7WaAAAAABV12zvvLs1QJQiBarKGmDGUEhYMzFFREdFMDIyMABFZGdl
|
|
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 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 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>0eN7WaAAAAADSA/Lwcwo7R7GTiJdFR7JJREVOMzAxMDAwMTA3MDMxAEVkZ2U=
|
|
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
|
|
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>0fN7WaAAAAACv9inO6UnuR5ODm/c2m2y5QlkzRURHRTAyMDkARWRnZQ==
|
|
Run ESLint & TypeScript compiler
Cache not found
|
|
Run ESLint & TypeScript compiler
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>0et7WaAAAAABbX8SZtZv5QL8NELA0MS0tREVOMzAxMDAwMTA3MDM5AEVkZ2U=
|
|
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>0fN7WaAAAAAAZkDXXlSf9Sr2qktWf5vMoREVOMzAxMDAwMTAyMDI5AEVkZ2U=
|
|
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 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>0et7WaAAAAADiHOhwv0bTQ76SkZ54pGciUEFPRURHRTA1MTYARWRnZQ==
|
|
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>0fd7WaAAAAAB372k0OwPaRK2u32VemcQPREVOMzAxMDAwMTA2MDQ3AEVkZ2U=
|
|
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>0jd7WaAAAAACapGC0yOKSQJfpWZnkh468UEhMMzBFREdFMDIxOABFZGdl
|
|
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
|