Skip to content
Build and release

Build and release #144

Sign in to view logs

Build and release

Build and release #144

Triggered via schedule March 18, 2026 02:59
@rampage644rampage644
⁠ f6c0dcf
main
Status Success
Total duration 26m 19s
Artifacts 4

build-and-release.yml.yml

on: schedule
Matrix: Build and Push Docker Image
merge
21s
merge
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build and Push Docker Image (linux/arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, 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. 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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L45
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JWT_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Build and Push Docker Image (linux/amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5, 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. 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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L45
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JWT_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, 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 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
Embucket~embucket~4BJ57B.dockerbuild
109 KB
sha256:ad09b80e27e929f169482bfb1b38166edfc274cc1499062284a81b85dd0c2fa4
Embucket~embucket~P45L03.dockerbuild
95.5 KB
sha256:71a0c1e4171c5e3cca7d6dfef8c8ffe101c28c5761800c78d6eedd2e502c5ce2
digests-linux-amd64 Expired
244 Bytes
sha256:2b02752cae60e6554264bcb797293452f630ee95ec28a25a3f688082b478bdea
digests-linux-arm64 Expired
244 Bytes
sha256:cd80e45728e0e1facaa563673e7024a7c91682b21e94f1a59bbfe4f241dbcc96