review changes #4431
nhsd-david-wasscicd-1-pull-request.yaml
on: push
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
35s
Commit stage
/
Check file format
10s
Commit stage
/
Check Markdown format
14s
Commit stage
/
Check English usage
15s
Commit stage
/
Check TODO usage
6s
Commit stage
/
Count lines of code
9s
Commit stage
/
Scan dependencies
56s
Commit stage
/
Check for changes to event schema package compared to main branch
7s
Commit stage
/
Check event schema version has been updated
Commit stage
/
Check for event schemas package version change
0s
Commit stage
/
Run terraform-docs
10s
Commit stage
/
Lint Terraform
25s
Test stage
/
Check generated dependencies
55s
Test stage
/
Pact tests
1m 7s
Test stage
/
Linting
3m 12s
Test stage
/
Typecheck
1m 54s
Test stage
/
Test coverage
4s
Test stage
/
Perform static analysis
1m 2s
Matrix: Build stage / Build OAS spec for main
Publish stage
/
Publish npm packages to npm.pkg.github.com
Publish stage
/
Publish nuget packages to nuget.pkg.github.com
Matrix: Publish stage / publish-oas-specs
Waiting for pending jobs
Publish stage
/
Success notification
Annotations
34 warnings
|
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
Commit stage / Lint Terraform
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: asdf-vm/actions/setup@1902764435ca0dd2f3388eea723a4f92a4eb8302. 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/
|
|
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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 stage / Check generated dependencies
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Pact 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 / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Typecheck
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Linting
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/validation.ts#L67
Generic Object Injection Sink
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/validation.ts#L41
Unsafe Regular Expression
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/common-ids.ts#L5
Prefer default export on a file with single export
|
|
Test stage / Linting:
lambdas/api-handler/src/utils/__tests__/validation.test.ts#L74
Test has no assertions
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/post-mi.ts#L5
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMIOperation`. Check if you meant to write `import postMI from '../services/mi-operations'` instead
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/utils/test-utils.ts#L3
Prefer default export on a file with single export
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/post-mi.test.ts#L7
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMiOperation`. Check if you meant to write `import postMI from '../../services/mi-operations'` instead
|
|
Test stage / Linting:
lambdas/api-handler/src/handlers/__tests__/amendment-event-transformer.test.ts#L123
Generic Object Injection Sink
|
|
Test stage / Linting:
internal/helpers/src/id-ref.ts#L54
Variable Assigned to Object Injection Sink
|
|
Test stage / Linting:
internal/datastore/src/letter-repository.ts#L64
Variable Assigned to Object Injection Sink
|
|
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
|
|
Build stage / Build Docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@983d7736d9b0ae728b81ab479565c72886d7745b, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@v4, ruby/setup-ruby@3783f195e29b74ae398d7caca108814bbafde90e. 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 / Build Docs
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ikT7aQAAAAD+QY98eztlQqDaYKsbPsXrQ0hHRURHRTE5MTYARWRnZQ==
|
|
Build stage / Build Docs
Failed to restore: Cache service responded with 400
|
|
Build stage / Build OAS spec for sandbox
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Build OAS spec for PR
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/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Build SDKs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
api-oas-specification-internal-dev-pr-1.1.6-20260506.133225+e997f67
|
20.7 KB |
sha256:443d3cbaec7a610ab85b98c2f59f90326372f05140d60d20480a4bb1854b4829
|
|
|
api-oas-specification-internal-dev-sandbox-1.1.6-20260506.133225+e997f67
|
20.9 KB |
sha256:675c5efbc6c0a50b7b7f23bc3a02a530a4c9937efe906fe9edf8387e99a1ac18
|
|
|
code-coverage-report
|
5.32 KB |
sha256:d31fad365e89ee800ce7df331618f0acbe88fdc1804ed194947d3126c6a386a8
|
|
|
jekyll-docs-1.1.6-20260506.133225+e997f67
|
1.4 MB |
sha256:7f61ff5c6340d69452ba6339cc665fcb9cd811288b1aee6e5c2aa752ec70dd18
|
|
|
lines-of-code-report.json.zip
|
988 Bytes |
sha256:8701ee8e0d0d71cea4a766bbe5606fe9b0306fd16d83278ac5210a51404a08e4
|
|
|
sbom-repository-report.json.zip
|
151 KB |
sha256:5fab3d5d55d1878ff8d0771258d983bf37f56810a7fd6da150463c0d2adb4ace
|
|
|
sdk-csharp-1.1.6-20260506.133225+e997f67
|
1 MB |
sha256:a302df07a666be299f6ca2c7ac0a294052fc59f3932e1a531dfb141637bd3098
|
|
|
sdk-html-1.1.6-20260506.133225+e997f67
|
8.54 KB |
sha256:efcc71bddc4e327c5b34af806f8284f51a78ba03b45e41adf02328e3820d0bcc
|
|
|
sdk-html-docs-1.1.6-20260506.133225+e997f67
|
9.31 KB |
sha256:9ebf0bb615b70b650e42ecf2831c3513eddd52476907d6f0c048e6bcb1c3502d
|
|
|
sdk-python-1.1.6-20260506.133225+e997f67
|
223 KB |
sha256:228ab69470d9b9e641addfd1e1e5471c98d40b7c9b859709224f21f6d4da4398
|
|
|
sdk-swagger-1.1.6-20260506.133225+e997f67
|
1.09 MB |
sha256:b7e5c80738b2afd028ef691f8d7ea04e62e6691583ac471ed99d3b1ca453bb2d
|
|
|
sdk-swagger-docs-1.1.6-20260506.133225+e997f67
|
1.09 MB |
sha256:86b9e437e16442747e6cb7409b29aa929a3d894578abdbdcf6a563c4f3dbde1f
|
|
|
sdk-ts-1.1.6-20260506.133225+e997f67
|
98.8 KB |
sha256:2770d2df8b3c1e7e7a4365c678c9962bc57875dcc5ef2021db36a67966373967
|
|
|
unit-tests
|
886 KB |
sha256:a0efa1170f5398d43d0b4fbee6cb430cbf9e5ac651c03dad09f43610a80669bc
|
|
|
vulnerabilities-repository-report.json.zip
|
26 KB |
sha256:5154898053b5ae534bedc163123a6d7d4903030344e78613545b46ad5e5bec16
|
|