Skip to content

Fix version formatting and enhance intro for auto-merge #47679

Fix version formatting and enhance intro for auto-merge

Fix version formatting and enhance intro for auto-merge #47679

Triggered via pull request October 21, 2025 23:31
Status Failure
Total duration 2m 38s
Artifacts

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 32 warnings
graphql
Process completed with exit code 1.
release-notes
Process completed with exit code 1.
workflows
Process completed with exit code 1.
content-render
Process completed with exit code 1.
assets
Process completed with exit code 1.
webhooks
Process completed with exit code 1.
events
Process completed with exit code 1.
audit-logs
Process completed with exit code 1.
shielding
Process completed with exit code 1.
data-directory
Process completed with exit code 1.
early-access
Process completed with exit code 1.
learning-track
Process completed with exit code 1.
secret-scanning
Process completed with exit code 1.
automated-pipelines
Process completed with exit code 1.
rest
Process completed with exit code 1.
redirects
Process completed with exit code 1.
content-linter
Process completed with exit code 1.
observability
Process completed with exit code 1.
archives
Process completed with exit code 1.
changelogs
Process completed with exit code 1.
frame
Process completed with exit code 1.
github-apps
Process completed with exit code 1.
products
Process completed with exit code 1.
color-schemes
Process completed with exit code 1.
versions
Process completed with exit code 1.
search
Process completed with exit code 1.
graphql
Failed to restore: Cache service responded with 400
release-notes
Failed to restore: Cache service responded with 400
workflows
Failed to restore: Cache service responded with 400
assets
Failed to restore: Cache service responded with 400
content-render
Failed to restore: Cache service responded with 400
webhooks
Failed to restore: Cache service responded with 400
events
Failed to restore: Cache service responded with 400
audit-logs
Failed to restore: Cache service responded with 400
shielding
Failed to restore: Cache service responded with 400
data-directory
Failed to restore: Cache service responded with 400
early-access
Failed to restore: Cache service responded with 400
learning-track
Failed to restore: Cache service responded with 400
secret-scanning
Failed to restore: Cache service responded with 400
automated-pipelines
Failed to restore: Cache service responded with 400
rest
Failed to restore: Cache service responded with 400
redirects
Failed to restore: Cache service responded with 400
content-linter
Failed to restore: Cache service responded with 400
observability
Failed to restore: Cache service responded with 400
archives
Failed to restore: Cache service responded with 400
changelogs
Failed to restore: Cache service responded with 400
frame
Failed to restore: Cache service responded with 400
github-apps
Failed to restore: Cache service responded with 400
products
Failed to restore: Cache service responded with 400
color-schemes
Failed to restore: Cache service responded with 400
versions
Failed to restore: Cache service responded with 400
landings
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>0Oxj4aAAAAADUUzMOE9XHRrEo1lbyy9IPQ0hJMzBFREdFMDMxNABFZGdl
landings
Failed to restore: Cache service responded with 400
article-api
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>0QBj4aAAAAAD29+w3Q/upR6lMFi/ThbllUEFPRURHRTA1MDcARWRnZQ==
article-api
Failed to restore: Cache service responded with 400
search
Failed to restore: Cache service responded with 400
fixtures
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>0cBj4aAAAAAAAFBygF2BlTpP6aMkInevjUEFPRURHRTA2MTgARWRnZQ==
fixtures
Failed to restore: Cache service responded with 400