create-release-deb: registry_pull_scope added #25
create-release-deb.yml
on: push
build_test
/
build
16m 20s
publish_runtime_image
/
publish
29s
publish_framework_image
/
publish
22s
Annotations
2 errors, 13 warnings, and 1 notice
|
publish_framework_image / publish
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/iit-dlslab/dls2-dev:latest: unexpected status from HEAD request to https://ghcr.io/v2/iit-dlslab/dls2-dev/manifests/latest: 403 Forbidden
|
|
publish_runtime_image / publish
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/iit-dlslab/dls2-dev:latest: unexpected status from HEAD request to https://ghcr.io/v2/iit-dlslab/dls2-dev/manifests/latest: 403 Forbidden
|
|
build_test / 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/upload-artifact@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/
|
|
build_test / test
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/download-artifact@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/
|
|
release_deb / 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, actions/download-artifact@v4, actions/upload-artifact@v4, mikepenz/release-changelog-builder-action@v5.0.0, paulhatch/semantic-version@v5.4.0. 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_framework_image / publish
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/download-artifact@v4, docker/build-push-action@0565240e2d4ab88bba5387d719585280857ece09, docker/login-action@343f7c4344506bcbf9b4de18042ae17996df046d, docker/metadata-action@96383f45573cb7f253c731d3b3ab81c87ef81934, docker/setup-buildx-action@f95db51fddba0c2d1ec667646a06c2ce06100226. 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_framework_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_framework_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_framework_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_framework_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_runtime_image / publish
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/download-artifact@v4, docker/build-push-action@0565240e2d4ab88bba5387d719585280857ece09, docker/login-action@343f7c4344506bcbf9b4de18042ae17996df046d, docker/metadata-action@96383f45573cb7f253c731d3b3ab81c87ef81934, docker/setup-buildx-action@f95db51fddba0c2d1ec667646a06c2ce06100226. 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_runtime_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_runtime_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_runtime_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
publish_runtime_image / publish
Unexpected input(s) 'scope', valid inputs are ['registry', 'username', 'password', 'ecr', 'logout']
|
|
release_deb / release
Remote tag v0.0.24 already exists. Skipping tag creation.
|