Skip to content

fix: close missing quote in notify-image-available PR comment body #2

fix: close missing quote in notify-image-available PR comment body

fix: close missing quote in notify-image-available PR comment body #2

Triggered via push May 21, 2026 17:33
Status Failure
Total duration 26m 32s
Artifacts
test  /  prepare-build
26s
test / prepare-build
Matrix: test / charts-validation
Waiting for pending jobs
Matrix: test / dockerfiles-validation
test  /  notify-image-available
3s
test / notify-image-available
Matrix: test / helm-charts-build
Matrix: test / services-build
test  /  ...  /  build-helmreleases
test / build-helmreleases / build-helmreleases
test  /  ...  /  create-gitops-deployments-pr
test / create-staging-pr / create-gitops-deployments-pr
Matrix: test / create-auto-merge-prod-pr
Waiting for pending jobs
test  /  ...  /  create-gitops-deployments-pr
test / create-manual-merge-prod-pr / create-gitops-deployments-pr
Matrix: test / wait-for-deployment
Waiting for pending jobs
test  /  ...  /  create-comment-with-pr-urls
test / create-comment-with-pr-urls / create-comment-with-pr-urls
test  /  ...  /  LCM-integration-e2e-tests
10m 52s
test / lcm-integration-e2e / LCM-integration-e2e-tests
test  /  ...  /  promote-to-stable
4s
test / promote-to-stable / promote-to-stable
test  /  ...  /  revert-staging-pr
test / revert-staging-pr / revert-staging-pr
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
test / promote-to-stable / promote-to-stable
failed to retrieve vault token. code: ERR_NON_2XX_3XX_RESPONSE, message: Response code 400 (Bad Request), vaultResponse: {"errors":["error validating claims: claim \"event_name\" does not match any associated bound claim values"]}
test / prepare-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@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/
test / services-build (lcm-bricks-nextversion)
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@v4, hashicorp/vault-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/
test / services-build (lcm-bricks)
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@v4, hashicorp/vault-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/
test / lcm-integration-e2e / LCM-integration-e2e-tests
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/
test / promote-to-stable / promote-to-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-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/