canary #505
Triggered via repository dispatch
April 2, 2026 21:44
actions-access-app[bot]
canary
ecdbe3e
Status
Failure
Total duration
3m 51s
Artifacts
–
publish-canary.yaml
on: repository_dispatch
Build and Publish Canary Image
3m 44s
Annotations
1 error and 3 warnings
|
Build and Publish Canary Image
buildx failed with: ERROR: failed to solve: failed to parse error response 400: <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>0M+TOaQAAAAA/+f9oBiD0RLmsQR9K18lgQ0hHRURHRTE3MTUARWRnZQ==: invalid character '<' looking for beginning of value
|
|
Build and Publish Canary Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/login-action@v2, docker/setup-buildx-action@v2, docker/setup-qemu-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build and Publish Canary Image
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>0YOPOaQAAAAA0aEIbxWJ9Q6v4x2imAYAoQ0hHRURHRTE3MTUARWRnZQ==
|
|
Build and Publish Canary Image
Failed to restore: Cache service responded with 400
|