Skip to content

Chore: [AEA-0000] - fix jira lambda call another way (#103) #86

Chore: [AEA-0000] - fix jira lambda call another way (#103)

Chore: [AEA-0000] - fix jira lambda call another way (#103) #86

Triggered via push March 23, 2026 10:24
Status Success
Total duration 5m 39s
Artifacts 1

release.yml

on: push
get_config_values  /  get_config_values
4s
get_config_values / get_config_values
get_config_values  /  verify_attestation
14s
get_config_values / verify_attestation
quality_checks  /  get_docker_images_to_scan
1m 26s
quality_checks / get_docker_images_to_scan
quality_checks  /  quality_checks
2m 57s
quality_checks / quality_checks
quality_checks  /  IaC-validation
1m 40s
quality_checks / IaC-validation
Matrix: quality_checks / docker_vulnerability_scan
tag_release  /  tag_release
2m 11s
tag_release / tag_release
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
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: 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
sbom.cdx.json
28.5 KB
sha256:5fe2be78f7a7863e08f46597d9513f9ff5bf99d71d714391825de96efb852ce9