Skip to content

CCM-15676 NHS App status handler (#294) #2588

CCM-15676 NHS App status handler (#294)

CCM-15676 NHS App status handler (#294) #2588

Triggered via push April 23, 2026 13:38
Status Failure
Total duration 6m 47s
Artifacts 7
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
17s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
8s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
7s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
12s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
50s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
6s
Commit stage / Detect Terraform Changes
Commit stage  /  Run terraform-docs
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Detect Schema Changes
4s
Test stage / Detect Schema Changes
Test stage  /  Unit tests
3m 31s
Test stage / Unit tests
Test stage  /  Check generated dependencies
0s
Test stage / Check generated dependencies
Test stage  /  Perform static analysis
1m 36s
Test stage / Perform static analysis
Build stage  /  Detect Documentation Changes
6s
Build stage / Detect Documentation Changes
Build stage  /  Build Docs
Build stage / Build Docs
Trigger dynamic environment creation
0s
Trigger dynamic environment creation
Publish stage  /  Publish packages
17s
Publish stage / Publish packages
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility test
Acceptance stage  /  Integration test
Acceptance stage / Integration test
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 16 warnings
Publish stage / Publish packages
Unable to download artifact(s): Artifact not found for name: jekyll-docs-0.0.2-20260423.133850+4e69b91 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
Test stage / Detect Schema Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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 stage / Contract tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 stage / Linting: src/typescript-schema-generator/src/generate-types.ts#L34
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: src/typescript-schema-generator/src/generate-guard-functions.ts#L51
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: lambdas/ttl-handle-expiry-lambda/src/__tests__/app/dlq.test.ts#L183
Variable Assigned to Object Injection Sink
Test stage / Linting: utils/utils/src/event-publisher/event-publisher.ts#L101
Function Call Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L47
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L34
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/config-reader.ts#L69
Variable Assigned to Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L52
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L33
Variable Assigned to Object Injection Sink
Test stage / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 stage / Perform static analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0. 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/
Build stage / Detect Documentation Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
Publish stage / Publish packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0. 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
code-coverage-report
17 KB
sha256:5c0b899b52cfcdc25d76b0b26fd535e8449c2636bde39ff099ee8057f38c46b9
lines-of-code-report.json.zip
962 Bytes
sha256:b17a35fd0c677f6442efb3b9790eb82bef44e9e9952ca4a4c1698d02b305e6a9
pact-contracts
609 Bytes
sha256:606e8f1ac147087dc8e09eaf1024a22329dd52b3f9693b4041a9e6e421148cd1
python-coverage-reports
13.4 KB
sha256:95f5b7852337eccc5efe2846af2f4a9ed211b23ec5ae41daec2ba99bc8ba52fe
sbom-repository-report.json.zip
392 KB
sha256:1f204c8f0f5ca3b7fc984fb736ed719164220389197039067efb4926955c67ed
unit-tests
1.95 MB
sha256:c2705fef75c9c46264967a67c3c2005e3c90769c8f382faae8ab7b8b9591b4e7
vulnerabilities-repository-report.json.zip
14.2 KB
sha256:a9c6f51606099d77b03ec8060b20afbe1fa6fb62d85e9c183d3f7f67732f7aa4