Skip to content

ci: add docker image build workflow and improve mcp tool handling (#194) #1

ci: add docker image build workflow and improve mcp tool handling (#194)

ci: add docker image build workflow and improve mcp tool handling (#194) #1

Triggered via push March 20, 2026 09:23
Status Failure
Total duration 9m 1s
Artifacts
Build Backend Image
3m 58s
Build Backend Image
Build Admin Portal Image
1m 43s
Build Admin Portal Image
Build Developer Portal Image
2m 11s
Build Developer Portal Image
Build Sandbox Image
8m 52s
Build Sandbox Image
Build Summary
4s
Build Summary
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
Build Admin Portal Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push opensource-registry.cn-hangzhou.cr.aliyuncs.com/himarket/himarket-admin:latest: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Build Developer Portal Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push opensource-registry.cn-hangzhou.cr.aliyuncs.com/himarket/himarket-frontend:latest: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Build Backend Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push opensource-registry.cn-hangzhou.cr.aliyuncs.com/himarket/himarket-backend:latest: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Build Sandbox Image
buildx failed with: ERROR: failed to build: failed to solve: failed to push opensource-registry.cn-hangzhou.cr.aliyuncs.com/himarket/himarket-sandbox:latest: push access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Build Summary
Unhandled error: SyntaxError: Unexpected identifier 'Portal'
Build Admin Portal Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Build Developer Portal Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Build Backend Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. 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/
Build Sandbox Image
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, docker/setup-qemu-action@v3. 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/
Build Summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/