CCM-16068 - Ensure we're using pnpm instead of npx #827
rhyscoxnhscicd-1-pull-request.yaml
on: push
Set CI/CD metadata
5s
Commit stage
/
Scan secrets
6s
Commit stage
/
Check file format
5s
Commit stage
/
Check Markdown format
6s
Commit stage
/
Check English usage
11s
Commit stage
/
Check TODO usage
4s
Commit stage
/
Count lines of code
9s
Commit stage
/
Scan dependencies
41s
Commit stage
/
Run terraform-docs
0s
Commit stage
/
Lint Terraform
0s
Test stage
/
Check generated dependencies
18s
Test stage
/
Linting
50s
Test stage
/
Typecheck
26s
Test stage
/
Test coverage
6s
Test stage
/
Perform static analysis
1m 16s
Build stage
/
Build Docs
48s
Build stage
/
Artefact 1
4s
Build stage
/
Artefact n
3s
Acceptance stage
/
Run Acceptance Tests
Annotations
1 error and 7 warnings
|
Create Dynamic Environment
Process completed with exit code 1.
|
|
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. 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. 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. 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. 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, ruby/setup-ruby@v1.180.1. 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>0ZlHOaQAAAABFPh2F0e5eSJKNcRLNJ9upUEhMMzBFREdFMDExNwBFZGdl
|
|
Build stage / Build Docs
Failed to restore: Cache service responded with 400
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
code-coverage-report
|
7.72 KB |
sha256:ff56bc20254cfae3cad612935eac6cdbfaee9c535d74a6347e0b85fc6067425f
|
|
|
jekyll-docs-0.0.2-20260402.111807+b6b6288
Expired
|
1.17 MB |
sha256:0dfc3573eef9ca9e1dabc2348dbc80549d4a9bb34a8b628e69af16cf2857d3e5
|
|
|
lines-of-code-report.json.zip
Expired
|
937 Bytes |
sha256:8ce1aaeddf5276b0e85c52aef0dd7fd7db3a562f43daa8e0e487d2c8d175bba1
|
|
|
sbom-repository-report.json.zip
Expired
|
171 KB |
sha256:22d62387e7aa8802a3b080f927c83f42901f25551b3d24ea537ecde748b3868e
|
|
|
unit-tests
|
1.03 MB |
sha256:880da8287e01335ccde01464f3baf17371fe5feeb1050a0d5834367088319d88
|
|
|
vulnerabilities-repository-report.json.zip
Expired
|
4.58 KB |
sha256:0a158fe588d8cc3df09377e9662d39af60584a92c116a5a5ea2d679855388a3b
|
|