Skip to content

Bump @redocly/cli from 2.29.1 to 2.29.2 in the npm-minor-patch group #2368

Bump @redocly/cli from 2.29.1 to 2.29.2 in the npm-minor-patch group

Bump @redocly/cli from 2.29.1 to 2.29.2 in the npm-minor-patch group #2368

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

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
25s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
33s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
5s
run-quality-checks / Lint Terraform projects
run-quality-checks  /  Test Coverage and SonarCloud
4m 8s
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
3m 37s
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) / wait-for-deployment
Process completed with exit code 1.
run-e2e-automation-tests (internal-dev-sandbox) / 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-1442-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
run-e2e-automation-tests (internal-dev-sandbox) / publish-test-report
Unable to download artifact(s): Artifact not found for name: dev-pr-1442-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
PR Deploy and Test
The strategy configuration was canceled because "run-e2e-automation-tests.internal-dev" failed
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 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 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 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/
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 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 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 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 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 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/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~46CXRV.dockerbuild
71 KB
sha256:02383d6b459232ba86f79d21f4387d30369c9d18d6eb2d921d7a3757237172a1
NHSDigital~immunisation-fhir-api~5V6DVL.dockerbuild
71.1 KB
sha256:68c285aca9fb4d2050bc08cf0a705cf265981bbdfaa796827cdbff0bbe26fb2c
NHSDigital~immunisation-fhir-api~7XMTQ1.dockerbuild
71.1 KB
sha256:e852b727a896afad48bf54516583417253f1fd0ca43520305634fcfbcedf984a
NHSDigital~immunisation-fhir-api~BXBNMH.dockerbuild
73.2 KB
sha256:507aa92f47c0f02fb1c84553fb79cf318083943ad52cebf021129f5c64c6511c
NHSDigital~immunisation-fhir-api~FD1G27.dockerbuild
71.3 KB
sha256:de99edc67144cd02a6102ed93a1b40f68f80418f4d3c557bdc07cf481a618e5a
NHSDigital~immunisation-fhir-api~OAGS72.dockerbuild
74.9 KB
sha256:f33a889131139a88578f7d8909de4379b1980577200f2fe3f459db057a0fdf87
NHSDigital~immunisation-fhir-api~OO7PG2.dockerbuild
73.2 KB
sha256:4490d6fd4f2608a79ad03fb0acbc41a543b134e2b0e87b3dfafc15ea0aa2ecbe
NHSDigital~immunisation-fhir-api~RMTEP0.dockerbuild
72.7 KB
sha256:fa3ed8628a50bfb6732183a0f8908a8beb44b10fd2421a9bccfff2420ba8d959
NHSDigital~immunisation-fhir-api~TA4S46.dockerbuild
71.7 KB
sha256:877d46f9326e2115ec56197c70b1ac5241126a93e712fb19e4e7676440ed8d81
NHSDigital~immunisation-fhir-api~YAA9IO.dockerbuild
71.1 KB
sha256:6b48cb839240fdac0b26402e3079d7ee448d29b4fe2ddc6eba274c607e9855ba
NHSDigital~immunisation-fhir-api~ZM84HV.dockerbuild
71.6 KB
sha256:aa369ce8b97b8b7fc8dfe1abb0bdbedf4206474cb7e96cd6828e22f4defc9eef
deploy-manifest-ack-backend-dev-pr-1442-1
626 Bytes
sha256:dcde981c7ad648e64aa8d31d9ff58cebd8f6faf1a241338eda4a242f7a44be8a
deploy-manifest-backend-dev-pr-1442-1
610 Bytes
sha256:250138be616c6b7ec10c60c2b20bbf6e61c5005146abaf408fc49d538a7529b0
deploy-manifest-batch_processor_filter-dev-pr-1442-1
656 Bytes
sha256:2bdc236cfabc9ca9ea36f1313e323e302a9a34d9f8434034fba1c2f3d072dc59
deploy-manifest-delta_backend-dev-pr-1442-1
629 Bytes
sha256:80086635985a2bda307b8a8b77c44243d4b2e398342f1b67f0b6affdfff4b9f4
deploy-manifest-filenameprocessor-dev-pr-1442-1
639 Bytes
sha256:37771f33e94e95f823f2f1e4dc4a87e6137e44c3abce04e10050fd004e01aa58
deploy-manifest-id_sync-dev-pr-1442-1
613 Bytes
sha256:adbc37b8ba146ff91f43ce4016127451bbdcc0706d73cb0646f2ff39c61ff7b9
deploy-manifest-mesh_processor-dev-pr-1442-1
632 Bytes
sha256:d65aadb8e5b0c14d4e80e5481d8a0bb715904973b9a8ca48ed844dc56ddce8b8
deploy-manifest-mns_publisher-dev-pr-1442-1
630 Bytes
sha256:19a8d27e3004a4ed5c480445f3730bdb7150c388273ef38926b11b99c60af0fa
deploy-manifest-recordforwarder-dev-pr-1442-1
632 Bytes
sha256:c7ec6072244366917278ef433b49bfe0c2e2f40c6ffb5d84a53a9d9888fb7a0c
deploy-manifest-recordprocessor-dev-pr-1442-1
632 Bytes
sha256:65d001d4da7bea132a08b2e1f11958100ab8e7047f6da8ced8fe3bed1234d16d
deploy-manifest-redis_sync-dev-pr-1442-1
622 Bytes
sha256:6db1eae677b5cca8ea2dc980dfe63e487f8d3327e2b3e4e0bb259743ffc48fee
dev-pr-1442-tfplan
98.4 KB
sha256:90e8d6e3c6ef9535217155cfec9da9005db9400f81a8ba552f16e91ba0001da6