Skip to content

.github/workflows/release.yml #23

.github/workflows/release.yml

.github/workflows/release.yml #23

Triggered via push April 15, 2026 08:01
Status Success
Total duration 14m 23s
Artifacts 4

release.yml

on: push
create-release
8s
create-release
Matrix: publish-images / build
Fit to window
Zoom out
Zoom in

Annotations

27 warnings
verify / Web Build
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, pnpm/action-setup@v4. 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/
verify / Go Tests
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-go@v5. 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/
create-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, softprops/action-gh-release@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/
publish-images / build (admin, deploy/docker/admin/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@v6, 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. 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/
publish-images / build (admin, deploy/docker/admin/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (admin, deploy/docker/admin/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (admin, deploy/docker/admin/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (admin, deploy/docker/admin/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (admin, deploy/docker/admin/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/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@v6, 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. 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/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (sing-box-gateway, deploy/docker/sing-box-gateway/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (control-plane, deploy/docker/control-plane/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@v6, 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. 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/
publish-images / build (control-plane, deploy/docker/control-plane/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (control-plane, deploy/docker/control-plane/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (control-plane, deploy/docker/control-plane/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (control-plane, deploy/docker/control-plane/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (control-plane, deploy/docker/control-plane/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (managed-user, deploy/docker/managed-user/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@v6, 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. 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/
publish-images / build (managed-user, deploy/docker/managed-user/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (managed-user, deploy/docker/managed-user/Dockerfile, .)
v2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (managed-user, deploy/docker/managed-user/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (managed-user, deploy/docker/managed-user/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/
publish-images / build (managed-user, deploy/docker/managed-user/Dockerfile, .)
2.0 is not a valid semver. More info: https://semver.org/

Artifacts

Produced during runtime
Name Size Digest
ZaneL1u~cloud-cli-proxy~E4MI2D.dockerbuild Expired
105 KB
sha256:783b3948f2b155f4f8f36add039c74b390a4619fedfdca659f8d1a93004b243d
ZaneL1u~cloud-cli-proxy~IVG4BZ.dockerbuild Expired
339 KB
sha256:d9354d5caf6f625ed10035f0934aff639375ae8b107dcc034993e64aaa83acc7
ZaneL1u~cloud-cli-proxy~IXW4TY.dockerbuild Expired
125 KB
sha256:673292bf5090cadeb1dae3c752d5b87fa8a63e7ac4701aa97d264c64a67ae0e7
ZaneL1u~cloud-cli-proxy~XZDW71.dockerbuild Expired
68.3 KB
sha256:676a1bbf298c6133bc4faa34006241ddf7ff97b04b3e335971ff6279f5b62885