CCM-16553: Code review comments #2636
nhsd-angel-pastorcicd-1-pull-request.yaml
on: push
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
16s
Commit stage
/
Check file format
4s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
10s
Commit stage
/
Check TODO usage
5s
Commit stage
/
Count lines of code
10s
Commit stage
/
Scan dependencies
1m 1s
Commit stage
/
Run terraform-docs
0s
Commit stage
/
Lint Terraform
0s
Test stage
/
Contract tests
53s
Test stage
/
Linting
2m 45s
Test stage
/
Typecheck
2m 6s
Publish stage
/
Publish packages
Acceptance stage
/
Security test
3s
Acceptance stage
/
UI test
6s
Acceptance stage
/
UI performance test
4s
Acceptance stage
/
Integration test
18m 16s
Acceptance stage
/
Accessibility test
4s
Acceptance stage
/
Load test
5s
Annotations
15 warnings
|
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-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:
scripts/nft-event-generator/src/utils/csv-reader.ts#L10
Found readFileSync from package "node:fs" with non literal argument at index 0
|
|
Test stage / Linting:
utils/utils/src/event-publisher/event-publisher.ts#L101
Function Call Object Injection Sink
|
|
Test stage / Linting:
utils/utils/src/event-publisher/event-publisher.ts#L99
Generic 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
code-coverage-report
|
17.1 KB |
sha256:de3e43ef96f5642d36f1d95843e5540d198eea930521cce43a2040ec3682b9cf
|
|
|
lines-of-code-report.json.zip
|
980 Bytes |
sha256:984cb09228a6bb90b930dd5b268587fcd1e644e21856aba38dc6067c997f46c8
|
|
|
pact-contracts
|
609 Bytes |
sha256:f2d08f8e89f8a8ec7ed756bc89a0975cf09a8bced322e47c2f9101f62d402279
|
|
|
python-coverage-reports
|
13.4 KB |
sha256:790d5c5669745238df2f0f7b34b8670a0195fb0611d893c4d3cec17afb7244a7
|
|
|
sbom-repository-report.json.zip
|
378 KB |
sha256:941d909a6de2e050193e552632ff6c14dfb9799b33221231f7f5c238e7ebcafc
|
|
|
unit-tests
|
1.98 MB |
sha256:2d32c641f868b92d9515af0f76cb261ecb69de69e9ef11d97cede80f978fecbd
|
|
|
vulnerabilities-repository-report.json.zip
|
4.44 KB |
sha256:482ae22e7d7575e2a29936958a01d8b8116b90fd86013abef1f88e366a9dfadf
|
|