CCM-16068 - CI fixes #825
rhyscoxnhscicd-1-pull-request.yaml
on: push
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
9s
Commit stage
/
Check file format
10s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
10s
Commit stage
/
Check TODO usage
3s
Commit stage
/
Count lines of code
7s
Commit stage
/
Scan dependencies
49s
Commit stage
/
Run terraform-docs
0s
Commit stage
/
Lint Terraform
Test stage
/
Check generated dependencies
19s
Test stage
/
Linting
53s
Test stage
/
Typecheck
29s
Test stage
/
Test coverage
5s
Test stage
/
Perform static analysis
1m 19s
Build stage
/
Artefact 1
Build stage
/
Artefact n
Build stage
/
Build Docs
Acceptance stage
/
Run Acceptance Tests
Annotations
1 error and 4 warnings
|
Test stage / Perform static analysis
Process completed with exit code 3.
|
|
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/setup-node@v4, pnpm/action-setup@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 / Typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@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 / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@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 / Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@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 | |
|---|---|---|---|
|
code-coverage-report
|
7.72 KB |
sha256:940473e54cafdfe1ac17f9fe15b28f4a63909e199c41224f66f69778e9d18d42
|
|
|
lines-of-code-report.json.zip
Expired
|
939 Bytes |
sha256:77da958f9b62c3de87f5f90e002f5f6d074c3e0a2bc2dd8d712d0732b585ae81
|
|
|
sbom-repository-report.json.zip
Expired
|
171 KB |
sha256:c8af50f949b2801abce641b37fbc595cec23ca91321b345657a939902799bd8f
|
|
|
unit-tests
|
1.03 MB |
sha256:94b1b09728366e0a32850d19d517a08dc44056e1a30e6e87a224bcd21bad8445
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
4.58 KB |
sha256:9dc930273fc6a5ed39613518c0c7ba7cab1a27bd8846017d804e847d02eec205
|
|