Skip to content

chore: add catalog-info.yaml for Backstage developer portal #63

chore: add catalog-info.yaml for Backstage developer portal

chore: add catalog-info.yaml for Backstage developer portal #63

Triggered via push March 24, 2026 05:24
Status Failure
Total duration 1m 27s
Artifacts 1

docker.yml

on: push
test-dev-alpine
1m 24s
test-dev-alpine
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
test-dev-alpine
buildx failed with: ERROR: failed to build: 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>0UiDCaQAAAAAuptxPfY1aR7uCyW0USO4gQ0hHRURHRTE3MTcARWRnZQ==: invalid character '<' looking for beginning of value
test-dev-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, docker/build-push-action@471d1dc4e07e5cdedd4c2171150001c434f0b7a4, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
BitGo~LavaMoat-ESM~SV0MW1.dockerbuild
36.9 KB
sha256:d2624e6b6229c237f536c6579305b4243399c88ceaa925710e81ff3c366125e7