Skip to content

fix: drizzel snapshot (#460) #1088

fix: drizzel snapshot (#460)

fix: drizzel snapshot (#460) #1088

Triggered via push May 19, 2026 07:15
Status Failure
Total duration 32s
Artifacts

release.yml

on: push
prepare-metadata
6s
prepare-metadata
Matrix: build-image
output-image-urls
output-image-urls
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
Build worker
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/***io/***-worker:-7501266": invalid reference format
Build builder
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/***io/***-builder:-7501266": invalid reference format
Build realtime
buildx failed with: ERROR: failed to build: invalid tag "ghcr.io/***io/***-realtime:-7501266": invalid reference format
prepare-metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@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/
prepare-metadata
v.0.2.5 is not a valid semver. More info: https://semver.org/
prepare-metadata
v.0.2.5 is not a valid semver. More info: https://semver.org/
Build worker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 0ndt/envfile@v2, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-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/
Build builder
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 0ndt/envfile@v2, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-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/
Build realtime
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 0ndt/envfile@v2, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-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/