Skip to content

Release Build Check #1133

Release Build Check

Release Build Check #1133

Triggered via schedule April 22, 2026 08:07
Status Failure
Total duration 1m 9s
Artifacts
latest-release
5s
latest-release
Matrix: clean-build
Matrix: verify-build-dockerized
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 3 warnings
verify-build-dockerized (ubuntu-22.04)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/internet-identity/internet-identity/.github/actions/slack'. Did you forget to run actions/checkout before running your local action?
verify-build-dockerized (ubuntu-22.04)
The process '/usr/bin/git' failed with exit code 128
verify-build-dockerized (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
verify-build-dockerized (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
verify-build-dockerized (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
verify-build-dockerized (ubuntu-20.04)
The strategy configuration was canceled because "verify-build-dockerized.ubuntu-22_04" failed
clean-build (ubuntu-22.04)
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/internet-identity/internet-identity/.github/actions/slack'. Did you forget to run actions/checkout before running your local action?
clean-build (ubuntu-22.04)
The process '/usr/bin/git' failed with exit code 128
clean-build (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
clean-build (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
clean-build (ubuntu-22.04)
couldn't find remote ref refs/tags/release-2026-04-21
clean-build (ubuntu-20.04)
The strategy configuration was canceled because "clean-build.ubuntu-22_04" failed
clean-build (macos-13)
The strategy configuration was canceled because "clean-build.ubuntu-22_04" failed
clean-build (macos-14)
The strategy configuration was canceled because "clean-build.ubuntu-22_04" failed
clean-build (macos-14)
The operation was canceled.
clean-build (macos-14)
couldn't find remote ref refs/tags/release-2026-04-21
clean-build (macos-14)
couldn't find remote ref refs/tags/release-2026-04-21
verify-build-dockerized (ubuntu-22.04)
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 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/
clean-build (ubuntu-22.04)
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 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/
clean-build (macos-14)
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 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/