Skip to content

Add priority to example_specifications.xlsx #258

Add priority to example_specifications.xlsx

Add priority to example_specifications.xlsx #258

Triggered via push April 23, 2026 19:38
Status Success
Total duration 3m 55s
Artifacts 7
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
12s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Markdown format
9s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
9s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
6s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
12s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
45s
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
7s
Commit stage / Detect Terraform Changes
Commit stage  /  Check event schema version has been updated
Commit stage / Check event schema version has been updated
Commit stage  /  Check for event schemas package version change
Commit stage / Check for event schemas package version change
Commit stage  /  Run terraform-docs
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
33s
Test stage / Check generated dependencies
Test stage  /  Linting
1m 34s
Test stage / Linting
Test stage  /  Typecheck
1m 1s
Test stage / Typecheck
Test stage  /  Integration tests
1m 2s
Test stage / Integration tests
Test stage  /  Unit tests
1m 36s
Test stage / Unit tests
Test stage  /  Test coverage
4s
Test stage / Test coverage
Test stage  /  Perform static analysis
5s
Test stage / Perform static analysis
Build stage  /  Build Docs
38s
Build stage / Build Docs
Build stage  /  Bundle ddb-publish CLI
38s
Build stage / Bundle ddb-publish CLI
Build stage  /  Artefact 1
6s
Build stage / Artefact 1
Build stage  /  Artefact n
4s
Build stage / Artefact n
Acceptance stage  /  Environment set up
4s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
3s
Acceptance stage / Contract test
Acceptance stage  /  Security test
3s
Acceptance stage / Security test
Acceptance stage  /  UI test
5s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
5s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
5s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
5s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
4s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
5s
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>083XqaQAAAAAGjKKbbDB8TIhd8ROWMB59Q08xRURHRTEyMjEARWRnZQ==
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
4.6 KB
sha256:3bbdf0204b413d6941e1b26783bd0c9ad5676f36fa432a4e8a2561f83694375a
ddb-publish-bundle
405 KB
sha256:ab5b9ea1be1a69d94de108912b4a7a4785ec203810bdc40a8268b899e149837f
jekyll-docs-1.0.0 Expired
117 KB
sha256:0d213e8deb26a9f7516d14dedb6e7e5ba55f92f06d558c72bc6ac65e99e1b8cb
lines-of-code-report.json.zip
899 Bytes
sha256:7b488031939a5c45a7f4205e1f843a5d611ed3a249e89bd3e0d830d5f2d933b3
sbom-repository-report.json.zip
34.5 KB
sha256:e0906577fef88c7d37b46c15672b3ff3f9c8c47711455e2a7e3293fec24368e8
unit-tests
479 KB
sha256:cea74d2169dbfbaf65e74e4e6e01c693d8030c9e4f94171be6a0c3f228ad88d9
vulnerabilities-repository-report.json.zip
5.37 KB
sha256:91594369792d5ff18ffc726932d8ad838a0ca10194a5e6723885517a00ee0b67