Skip to content

CCM-17221: Add priority field to LetterVariant schema (#58) #249

CCM-17221: Add priority field to LetterVariant schema (#58)

CCM-17221: Add priority field to LetterVariant schema (#58) #249

Triggered via push April 20, 2026 14:20
Status Success
Total duration 3m 46s
Artifacts 7
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
14s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
8s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
4s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
44s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
5s
Commit stage / Check for changes to event schema package compared to main branch
Commit stage  /  Detect Terraform Changes
3s
Commit stage / Detect Terraform Changes
Commit stage  /  Check event schema version has been updated
0s
Commit stage / Check event schema version has been updated
Commit stage  /  Check for event schemas package version change
0s
Commit stage / Check for event schemas package version change
Commit stage  /  Run terraform-docs
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
41s
Test stage / Check generated dependencies
Test stage  /  Linting
1m 21s
Test stage / Linting
Test stage  /  Typecheck
1m 9s
Test stage / Typecheck
Test stage  /  Integration tests
55s
Test stage / Integration tests
Test stage  /  Unit tests
1m 31s
Test stage / Unit tests
Test stage  /  Test coverage
6s
Test stage / Test coverage
Test stage  /  Perform static analysis
6s
Test stage / Perform static analysis
Build stage  /  Build Docs
33s
Build stage / Build Docs
Build stage  /  Bundle ddb-publish CLI
38s
Build stage / Bundle ddb-publish CLI
Build stage  /  Artefact 1
3s
Build stage / Artefact 1
Build stage  /  Artefact n
4s
Build stage / Artefact n
Acceptance stage  /  Environment set up
3s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
3s
Acceptance stage / Contract test
Acceptance stage  /  Security test
5s
Acceptance stage / Security test
Acceptance stage  /  UI test
4s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
4s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
4s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
5s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
3s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
3s
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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@d3f86a106a0bac45b974a628896c90dbdf5c8093. 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@49933ea5288caeca8642d1e84afbd3f7d6820020, 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>0AzfmaQAAAAA5pA+mr3OQQ6EvIJvpr/QKUEhMMzBFREdFMDIxNgBFZGdl
Build stage / Build Docs
Failed to restore: Cache service responded with 400
Build stage / Bundle ddb-publish CLI
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@65c4c4a1ddee5b72f698fdd19549f0f0fb45cf08. 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
1.63 KB
sha256:17393c3d5c6c6a798ddacbbc06103da18984cb36b71433f3bb208481917242f4
ddb-publish-bundle
403 KB
sha256:c9d35a28feb95515284c57bf2b38cfc7c1eac705e9370accaf0d0a9754013b91
jekyll-docs-1.0.0 Expired
117 KB
sha256:93627b8fe4fcbfe9e36daefd1dd4a7176daa61c19ce9555e6b9027ea2b8e1cee
lines-of-code-report.json.zip
885 Bytes
sha256:b2e088ac8930206cffc443a593c28fee60cf3d75f2194aefaebf21051abdf0cb
sbom-repository-report.json.zip
31.9 KB
sha256:2af2879d7423d04825c372ff0906e787713fede9b2aa2d4eaf7568a099c44238
unit-tests
356 KB
sha256:e7517a5e650aaa57f67b45d4530ec5453017636544732d9970a11da296370bb1
vulnerabilities-repository-report.json.zip
4.61 KB
sha256:e5d4096ffd0615aaa412d141b3c161a1b0f7b242901341e0186c98fc253bf4f7