Skip to content

VED-1233: Replace manual release steps #2342

VED-1233: Replace manual release steps

VED-1233: Replace manual release steps #2342

Triggered via pull request April 22, 2026 10:19
Status Success
Total duration 36m 43s
Artifacts 25

pr-deploy-and-test.yml

on: pull_request
run-quality-checks  /  Lint specification
18s
run-quality-checks / Lint specification
run-quality-checks  /  Lint Python projects
32s
run-quality-checks / Lint Python projects
run-quality-checks  /  Lint Terraform projects
7s
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
34s
deploy-pr-backend / terraform-plan
deploy-pr-backend  /  terraform-apply
3m 42s
deploy-pr-backend / terraform-apply
Matrix: run-e2e-automation-tests
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
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 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 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 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 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 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 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 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 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 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/

Artifacts

Produced during runtime
Name Size Digest
NHSDigital~immunisation-fhir-api~05CDB3.dockerbuild
70.4 KB
sha256:ca2f177be791a3c5cf65875fc27c39c8450572d7fbd5c9ff6ec157e89a2b6947
NHSDigital~immunisation-fhir-api~0EG2LS.dockerbuild
66.3 KB
sha256:333c54c6634761e11b177b698e005d0be481fcf7338ec95954ce244a648027ff
NHSDigital~immunisation-fhir-api~4D2YUZ.dockerbuild
69.8 KB
sha256:5beeb5629e534d3e4d9924420ff9e8f38a7e84d9990456e449db60988d2c7838
NHSDigital~immunisation-fhir-api~8CICF6.dockerbuild
69.1 KB
sha256:c51cf27ac4fd59bd2890c5b0f16d1a6f29550a2c2ea90cb7e1535dbba09db4fa
NHSDigital~immunisation-fhir-api~8Y7A6F.dockerbuild
70.9 KB
sha256:8c69683cb64fea1faf43eaac51ff81cc71a46745e915cd1bf2e690c13a67d52a
NHSDigital~immunisation-fhir-api~J9XL6L.dockerbuild
67.6 KB
sha256:6c55c1fd5b0590ed64f74c7cc4632bdd639e9e558cd9adf178233e6324860c2f
NHSDigital~immunisation-fhir-api~JOMEIE.dockerbuild
68.5 KB
sha256:9b7e96f7167fa2099ea090d9830e91069c4524b4061a493c93c69675e4ad54ce
NHSDigital~immunisation-fhir-api~SNAMPR.dockerbuild
68.6 KB
sha256:59efc71c872099ff048cb5b8e6c45e9d3536e5bb1e8e293c1b43334d4bf9f580
NHSDigital~immunisation-fhir-api~SQBF09.dockerbuild
39.2 KB
sha256:25193ba3d46712ec46401c66d1028cd4ba5c72d8af8c4a4e803b89bd8fd01fd7
NHSDigital~immunisation-fhir-api~UMSRC7.dockerbuild
68.2 KB
sha256:0a79357c5706acdeb0fa9726631b904a2003394ff90fa043fb00275470378ebb
NHSDigital~immunisation-fhir-api~WKNQKX.dockerbuild
69 KB
sha256:7c44ec17762a553fcb485ca1dc83241484877e839fbbcf3b0b685cf7729e9bdc
deploy-manifest-ack-backend-dev-pr-1437-1
627 Bytes
sha256:a479a5224f9f7c6cd7ec9bea034ff5dcf4ee82dea1b47750221645e8adaa4eb5
deploy-manifest-backend-dev-pr-1437-1
610 Bytes
sha256:ea43f206e77cf90a0c5911dac2a04d2a9e3982ca8d5103aece8e18803d1a442c
deploy-manifest-batch_processor_filter-dev-pr-1437-1
656 Bytes
sha256:86c25a68d2134a70b59ed00bceeccc9c02861a9009a75c7d35eed90e32f686df
deploy-manifest-delta_backend-dev-pr-1437-1
630 Bytes
sha256:237a3cc1dd5f864b4fb010e59800c748e15080d9e88a11c0c13a33f2c5371e62
deploy-manifest-filenameprocessor-dev-pr-1437-1
639 Bytes
sha256:2bc8ffe5b302eed6bf8e97b69259d020900b22d28116d386b51260383baed449
deploy-manifest-id_sync-dev-pr-1437-1
613 Bytes
sha256:4c9b544b1fba32468aac4bd643f61fff97cd8dbcf89eb9f366930fb1cd9c07a4
deploy-manifest-mesh_processor-dev-pr-1437-1
633 Bytes
sha256:58e4805995525dbc1c215704dfd0afda07b21772f8473dd669ac71cb3c77f650
deploy-manifest-mns_publisher-dev-pr-1437-1
632 Bytes
sha256:4ad0bd2b68e71da065c7057504f4597bfffe52fc1c1ce14893420f932d5128c2
deploy-manifest-recordforwarder-dev-pr-1437-1
633 Bytes
sha256:541f43d99754cf1dbf16cb54cb1ee18d6d590f3105e652672560d10dffcff5ec
deploy-manifest-recordprocessor-dev-pr-1437-1
633 Bytes
sha256:e49983f8eb6efb4ca0d07c5381cf98f7cf1b919f3e8ed8631ebb476ef5c372ef
deploy-manifest-redis_sync-dev-pr-1437-1
621 Bytes
sha256:f672a97b2be390d807712efc5777a60af37460f84430f23bb288b99c30965fb4
dev-pr-1437-internal-dev-e2e-test-output
558 KB
sha256:93e5f26a914ecb149ba199c01a65d5f63e1f9251a1896fc082d4fb6985f470db
dev-pr-1437-internal-dev-sandbox-e2e-test-output
9.47 KB
sha256:cbd0ba98ce97edb60d1e013a539600eebb884031ab1690ea4ba9bc3467bb23f6
dev-pr-1437-tfplan
98.3 KB
sha256:47fe6c942d70507e7cd41665508c0eb1a54487160dc4c168f42c3f106c57bc4f