Skip to content

Bump actions/setup-node from 6.3.0 to 6.4.0 (#194) #2931

Bump actions/setup-node from 6.3.0 to 6.4.0 (#194)

Bump actions/setup-node from 6.3.0 to 6.4.0 (#194) #2931

Triggered via push April 28, 2026 09:13
Status Success
Total duration 4m 47s
Artifacts 9
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
22s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Python format
6s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
16s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
10s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 11s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
5s
Test stage / Create coverage artefact name
Test stage  /  Unit tests
45s
Test stage / Unit tests
Test stage  /  Contract tests
1m 10s
Test stage / Contract tests
Test stage  /  Schema validation tests
1m 25s
Test stage / Schema validation tests
Test stage  /  Integration tests
1m 7s
Test stage / Integration tests
Test stage  /  Acceptance tests
1m 14s
Test stage / Acceptance tests
Test stage  /  Merge test coverage
45s
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
1m 2s
Test stage / SonarCloud Analysis
Build stage  /  Artefact 1
Build stage / Artefact 1
Build stage  /  Artefact 2
Build stage / Artefact 2
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
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
Acceptance stage  /  Environment tear down
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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 / Integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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 / Acceptance tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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 / Schema validation tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: test-summary/action@31493c76ec9e7aa675f1585d3ed6f1da69269a86. 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
acceptance-test-results
113 KB
sha256:be1b62950dc756f7b8df1c8a9b3ae81de2378a61136f916c26377700bbdbf171
contract-test-results
117 KB
sha256:a6e491fd5e2dcb13cc89ff7c95df573fff44829e3b1edc34a51f511660a2b62b
coverage-main-2931
794 KB
sha256:30ecdcbae1312d5c6d3fb1bc990b74fbcc47eb44af3e6dfc760f66a68568eae3
integration-test-results
114 KB
sha256:6ac4a448e485d9e08d466830be553a931da4313a64ef2ed647ff1d351f365842
lines-of-code-report.json.zip
858 Bytes
sha256:d98e11b2f0e4b4af59c472baa299db36f29a84b045c9bf82033a726ac0548d9c
sbom-repository-report.json.zip
96.7 KB
sha256:14d5ee695586b6ee7f72e47f163ec498b8eff2e90b0bd8117b9aa18aff20039c
schema-test-results
113 KB
sha256:43581d09c78249890a7fcf33539ecd45aecc7ef3a7a6bf777af466b71377b9d0
unit-test-results
235 KB
sha256:17a87f9963ec2756b04c0c46b290822c8d5f1316dc30959f36ffea43763bfb13
vulnerabilities-repository-report.json.zip
4.03 KB
sha256:7f0df8b09d4236a7f943119d2eb3c8fd913699baea6a0d7bcce56f483af2e9d4