Skip to content

Bump @redocly/cli from 2.28.1 to 2.29.0 in the npm-minor-patch group #2322

Bump @redocly/cli from 2.28.1 to 2.29.0 in the npm-minor-patch group

Bump @redocly/cli from 2.28.1 to 2.29.0 in the npm-minor-patch group #2322

Triggered via pull request April 21, 2026 02:23
Status Failure
Total duration 26m 55s
Artifacts 23

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
21s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
32s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
9s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
4m 13s
run-quality-checks / Test Coverage and SonarCloud
Matrix: deploy-pr-backend / deploy-lambda-images
deploy-pr-backend  /  terraform-plan
41s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
4m 6s
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 11 warnings
run-e2e-automation-tests (internal-dev-sandbox) / wait-for-deployment
Process completed with exit code 1.
run-e2e-automation-tests (internal-dev) / wait-for-deployment
Process completed with exit code 1.
run-e2e-automation-tests (internal-dev) / publish-test-report
Unable to download artifact(s): Artifact not found for name: dev-pr-1431-internal-dev-e2e-test-output Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
PR Deploy and Test
The strategy configuration was canceled because "run-e2e-automation-tests.internal-dev" failed
run-e2e-automation-tests (internal-dev-sandbox) / publish-test-report
Unable to download artifact(s): Artifact not found for name: dev-pr-1431-internal-dev-sandbox-e2e-test-output Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
deploy-pr-backend / Deploy delta_backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy batch_processor_filter image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy id_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy recordforwarder image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy redis_sync image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy mesh_processor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy mns_publisher image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy filenameprocessor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy recordprocessor image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
deploy-pr-backend / Deploy ack-backend image / Build or reuse image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~4J2XAO.dockerbuild
40.4 KB
sha256:049e29c864296a19f233bf7ab59b62542fe709cb0693d21d327bfbd1bdd572d2
NHSDigital~immunisation-fhir-api~4LURP6.dockerbuild
39.4 KB
sha256:8ffa80bf6a719988c0579359b8d5f096190d0952ba4256ed4bb13023cebd29e5
NHSDigital~immunisation-fhir-api~4W5773.dockerbuild
39 KB
sha256:55b5e62a08e6271eeaa0ac4c35b44fd7f71141c91a037acb65fade7249335f18
NHSDigital~immunisation-fhir-api~GX7OVV.dockerbuild
39.9 KB
sha256:c56efdcd0f2e45ffb0172abb58e99ae82f20da875afe37bda4d52c510647e300
NHSDigital~immunisation-fhir-api~KP8QBW.dockerbuild
40.6 KB
sha256:d9c17ffef96b48cc110ede960625dcbdcf597e9814562f441f215d437f7514fc
NHSDigital~immunisation-fhir-api~MHNFWR.dockerbuild
67.2 KB
sha256:323122c092a8521d6c2965c5739b460f446f33e4c717182d076c0a471c0054d3
NHSDigital~immunisation-fhir-api~MQRKGX.dockerbuild
39.8 KB
sha256:123781400bed2bcfdd6e487838b4a722433f39167fd9ea3c1ee796bed1e7512a
NHSDigital~immunisation-fhir-api~PG9DQO.dockerbuild
38.5 KB
sha256:5736826ae0634276677a8308c483a27bc4e9010b1d4232d08266b9ad51ee7aa8
NHSDigital~immunisation-fhir-api~WI56RW.dockerbuild
39.8 KB
sha256:d4ba4a00352294ff57d3ba951c927a4753b744e6d96d1e08dc596d80f28a5858
NHSDigital~immunisation-fhir-api~XGG8VZ.dockerbuild
67.2 KB
sha256:eb489c1c18b4bed2f619f2539c72450dd589a675be684fb5cca4f622ac6fc9e4
NHSDigital~immunisation-fhir-api~YOV0Z4.dockerbuild
38.8 KB
sha256:093237b952f34ad07197d61e4fd52efbd610c53ce6bb7fed2e74e56d19a05c85
deploy-manifest-ack-backend-dev-pr-1431-1
627 Bytes
sha256:9868aaf03ce21a68eeea12dab2bccf7760d8e958277edaef77146a509036253b
deploy-manifest-backend-dev-pr-1431-1
611 Bytes
sha256:8452464b6a2e457fe77403b50a4b1bdd3699397ea2d5de8ab899a8636368c4d2
deploy-manifest-batch_processor_filter-dev-pr-1431-1
657 Bytes
sha256:e70d4f026aa07f1b8dd191b0e33c7a4c4f43bd440f071a709fc28b877ab1a490
deploy-manifest-delta_backend-dev-pr-1431-1
630 Bytes
sha256:88382d4a9702716b5a2a6330f9271ac257e49ad3e951b1270d6391248fdfa493
deploy-manifest-filenameprocessor-dev-pr-1431-1
638 Bytes
sha256:430cfd01af5b18c5679441433c4ccfeebc3ea9ca9abd22a37f3946fb6ad263f5
deploy-manifest-id_sync-dev-pr-1431-1
613 Bytes
sha256:b8650373ff5a94c6239f9bb6101d4006e38cd2004441f9d46733025dd267a0c9
deploy-manifest-mesh_processor-dev-pr-1431-1
633 Bytes
sha256:08ddbc257ac9553e343722b24c551086a3fe9058ac98d77db0de2d69d0f2fbbe
deploy-manifest-mns_publisher-dev-pr-1431-1
630 Bytes
sha256:8e8d703e86ee1612cf0901bc978c1e013e12837847855b246c89fbd344f68ada
deploy-manifest-recordforwarder-dev-pr-1431-1
633 Bytes
sha256:b42c4ecefd5a4c5a8c3600201a160c27a9db592481b5a232568c61fbcbe51c9f
deploy-manifest-recordprocessor-dev-pr-1431-1
632 Bytes
sha256:2e0f806f16a7eee59a06637668c2cd7d95e12c1d9581acb011d705e298668b34
deploy-manifest-redis_sync-dev-pr-1431-1
622 Bytes
sha256:81d2045a575ff6b9b2dff57eab2d7da6725b1e4d177cd92c89579deadf34c05d
dev-pr-1431-tfplan
98.9 KB
sha256:3baee06215e5ee6ca5f99cb7f71f84f88f187920a64ee9e9cd2d6a64453433c7