Skip to content

Promote to main: MCP + UI defect fixes from skeptical audit #138

Promote to main: MCP + UI defect fixes from skeptical audit

Promote to main: MCP + UI defect fixes from skeptical audit #138

Triggered via pull request June 13, 2026 17:57
Status Failure
Total duration 25s
Artifacts

docker-publish.yml

on: pull_request
Matrix: build-and-push
build-stack
build-stack
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
build-and-push (web, ., packages/web/Dockerfile)
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/graphdone/graphdone-web:-69c4029": invalid reference format
build-and-push (neo4j, ., deployment/neo4j.Dockerfile)
The strategy configuration was canceled because "build-and-push.web___packages_web_Docker" failed
build-and-push (neo4j, ., deployment/neo4j.Dockerfile)
The operation was canceled.
build-and-push (api, ., packages/server/Dockerfile)
The strategy configuration was canceled because "build-and-push.web___packages_web_Docker" failed
build-and-push (api, ., packages/server/Dockerfile)
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/graphdone/graphdone-api:-69c4029": invalid reference format
build-and-push (web, ., packages/web/Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-push (neo4j, ., deployment/neo4j.Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-push (api, ., packages/server/Dockerfile)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/