Skip to content

deploy to environments #75

deploy to environments

deploy to environments #75

Manually triggered March 18, 2026 16:16
Status Failure
Total duration 30d 0h 10m 14s
Artifacts 2

release.yml

on: workflow_dispatch
get_commit_id
2s
get_commit_id
get_config_values  /  get_config_values
6s
get_config_values / get_config_values
get_config_values  /  verify_attestation
8s
get_config_values / verify_attestation
quality_checks  /  get_docker_images_to_scan
1m 16s
quality_checks / get_docker_images_to_scan
quality_checks  /  quality_checks
3m 21s
quality_checks / quality_checks
quality_checks  /  IaC-validation
2m 7s
quality_checks / IaC-validation
Matrix: quality_checks / docker_vulnerability_scan
tag_release  /  tag_release
2m 19s
tag_release / tag_release
package_code  /  package_code
1m 56s
package_code / package_code
release_dev  /  release_code
1m 55s
release_dev / release_code
release_qa  /  release_code
30d 0h
release_qa / release_code
qa review time expired
release_ref  /  release_code
30d 0h
release_ref / release_code
ref review time expired
release_int  /  release_code
release_int / release_code
release_prod  /  release_code
release_prod / release_code
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
release_ref / release_code
The deployment was rejected or didn't satisfy other protection rules.
release_qa / release_code
The deployment was rejected or didn't satisfy other protection rules.
quality_checks / quality_checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: SonarSource/sonarqube-scan-action@a31c9398be7ace6bbfaf30c0bd5d415f843d45e9. 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/
tag_release / tag_release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@00943011d9042930efac3dcd3a170e4273319bc8, cardinalby/git-get-release-action@5172c3a026600b1d459b117738c605fabc9e4e44. 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
build_artifact
74.6 MB
sha256:5711e25e570ee698082ebcf8b9a136b39fb99ac44731da24e6cd28aba0a7106e
sbom.cdx.json
17.9 KB
sha256:34e940da6bf34843eee1242f96bc490c149061298760a80ed7a5f52e4e7351b9