Skip to content

CCM-16444: Config seeding for dynamic envs (#532) #4324

CCM-16444: Config seeding for dynamic envs (#532)

CCM-16444: Config seeding for dynamic envs (#532) #4324

Triggered via push April 28, 2026 08:19
Status Failure
Total duration 9m 39s
Artifacts 19
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
33s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file 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  /  Check TODO usage
6s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
54s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
7s
Commit stage / Check for changes to event schema package compared to main branch
Commit stage  /  Detect Terraform Changes
5s
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
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
52s
Test stage / Check generated dependencies
Test stage  /  Pact tests
1m 10s
Test stage / Pact tests
Test stage  /  Linting
3m 14s
Test stage / Linting
Test stage  /  Typecheck
1m 54s
Test stage / Typecheck
Test stage  /  Unit tests
2m 52s
Test stage / Unit tests
Test stage  /  Test coverage
6s
Test stage / Test coverage
Test stage  /  Perform static analysis
1m 8s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 45s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
4m 2s
Build stage / Create Dynamic Environment
Matrix: Build stage / artefact-oas-spec
Build stage  /  Build OAS spec for sandbox
1m 5s
Build stage / Build OAS spec for sandbox
Build stage  /  Populate Supplier Config
Build stage / Populate Supplier Config
Build stage  /  Build SDKs
1m 26s
Build stage / Build SDKs
Build stage  /  Build proxies
Build stage / Build proxies
Acceptance stage  /  Run Acceptance Tests
Acceptance stage / Run Acceptance Tests
Acceptance stage  /  Run End-to-End Tests
Acceptance stage / Run End-to-End Tests
Publish stage  /  Publish packages
Publish stage / Publish packages
Publish stage  /  Publish npm packages to npm.pkg.github.com
Publish stage / Publish npm packages to npm.pkg.github.com
Publish stage  /  Publish nuget packages to nuget.pkg.github.com
Publish stage / Publish nuget packages to nuget.pkg.github.com
Matrix: Publish stage / publish-oas-specs
Waiting for pending jobs
Publish stage  /  Success notification
Publish stage / Success notification
Fit to window
Zoom out
Zoom in

Annotations

1 error and 37 warnings
Build stage / Create Dynamic Environment
Process completed with exit code 1.
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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 / 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/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Check generated dependencies
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Pact tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830. 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 / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Pact tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
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/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Typecheck
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
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/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Unit tests
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
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/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
Test stage / Linting: lambdas/api-handler/src/utils/validation.ts#L67
Generic Object Injection Sink
Test stage / Linting: lambdas/api-handler/src/utils/common-ids.ts#L5
Prefer default export on a file with single export
Test stage / Linting: lambdas/api-handler/src/handlers/post-mi.ts#L5
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMIOperation`. Check if you meant to write `import postMI from '../services/mi-operations'` instead
Test stage / Linting: lambdas/api-handler/src/handlers/__tests__/utils/test-utils.ts#L3
Prefer default export on a file with single export
Test stage / Linting: lambdas/api-handler/src/handlers/__tests__/post-mi.test.ts#L7
Caution: `mi-operations.ts` has a default export `postMI`. This imports `postMI` as `postMiOperation`. Check if you meant to write `import postMI from '../../services/mi-operations'` instead
Test stage / Linting: internal/helpers/src/id-ref.ts#L54
Variable Assigned to Object Injection Sink
Test stage / Linting: internal/datastore/src/letter-repository.ts#L64
Variable Assigned to Object Injection Sink
Test stage / Linting
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
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@983d7736d9b0ae728b81ab479565c72886d7745b, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@v4, ruby/setup-ruby@3783f195e29b74ae398d7caca108814bbafde90e. 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>0KW/waQAAAAAxAsVEFS5GTIFh9lhCLwoFUEhMMzBFREdFMDIxMgBFZGdl
Build stage / Build Docs
Failed to restore: Cache service responded with 400
Build stage / Build OAS spec (internal-dev-pr)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 OAS spec (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 OAS spec (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 OAS spec (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 OAS spec for sandbox
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 OAS spec (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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 SDKs
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@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
api-oas-specification-int-1.1.6-20260428.082003+830c5ba
20.9 KB
sha256:3263a80ad0b4753bf9a183be1b703dcd0db3f5758b1b5faa3e882e31d395af39
api-oas-specification-internal-dev-1.1.6-20260428.082003+830c5ba
20.9 KB
sha256:51aabc1b1308b683fc937b3a9f4e7f3889cd4845215eedb7fae66a946fdfb814
api-oas-specification-internal-dev-pr-1.1.6-20260428.082003+830c5ba
20.7 KB
sha256:5e97d62985bcb37519416e4f2f45e0a70268995c1c9e29ce433ec1f18589102a
api-oas-specification-internal-dev-sandbox-1.1.6-20260428.082003+830c5ba
20.9 KB
sha256:b032b1012713aedd869af103f3aecdd2aedced981625981ca66ad0a65427708d
api-oas-specification-prod-1.1.6-20260428.082003+830c5ba
20.9 KB
sha256:d79556c8a2558e4571246ce39b28573016ee34afc75dc79c719903af3b948b5a
api-oas-specification-ref-1.1.6-20260428.082003+830c5ba
20.9 KB
sha256:5254d8ec116057da1b3a8f2ddf1171a1873ee7a9f7076ead54eaf09ae23af703
code-coverage-report
4.58 KB
sha256:75d70f81ccae17ead938a4224802cae0b0d0b04f1e5559961911b857120a9f62
jekyll-docs-1.1.6-20260428.082003+830c5ba Expired
1.4 MB
sha256:9e0212f3545ffc7ac67ea12d7e3f670ceb56d54024cb5521339d6381b575fb32
lines-of-code-report.json.zip Expired
963 Bytes
sha256:33ebe3ee12acae4dfb04a0bf2f99070ca2180e0f46ea01c15f06aad89c728d79
sbom-repository-report.json.zip Expired
148 KB
sha256:d4fd2f02779a3bb619cd9686277c11fb6ab7ddf7ec48c0625572aa4f73a83a2b
sdk-csharp-1.1.6-20260428.082003+830c5ba
1020 KB
sha256:c77b3012f6768a8ecc916834ec886b6e8f330bb7fb5d94187a0bc5405d5e369b
sdk-html-1.1.6-20260428.082003+830c5ba
8.54 KB
sha256:78f3c38fe6fa3def5c86bd3046c68f5b656e85c10015b7e30cfbc2e34ca8f95e
sdk-html-docs-1.1.6-20260428.082003+830c5ba Expired
9.31 KB
sha256:6acf96d95184c5b97e281341c9db22994773bd9772b293894f2ec131a43019f8
sdk-python-1.1.6-20260428.082003+830c5ba
223 KB
sha256:7e39a38e73fd5d934647a016eb5a2b31702d9a295e5b9ebf364dfe17b3751677
sdk-swagger-1.1.6-20260428.082003+830c5ba
1.09 MB
sha256:4ec4c32c99ed8b8a0307fbe31943af2e1906b5906a62930d6ab7db34a9e5b589
sdk-swagger-docs-1.1.6-20260428.082003+830c5ba Expired
1.09 MB
sha256:cb698d14997f0ddea93494b164fe2eaef76554fa75deb8cc8709aad1c53aa7c6
sdk-ts-1.1.6-20260428.082003+830c5ba
98.8 KB
sha256:cab2a3e103526e2c1882a5b487230c4c7f4d8f96a5d28a8c5884fcd765b9ab6a
unit-tests
837 KB
sha256:2f64b11b9cb13f3ce0bc8fe94e566fc848b9471ef9c0c3b83f35d98602d44a24
vulnerabilities-repository-report.json.zip Expired
20.1 KB
sha256:5404be155978a4ad3a2293b5cd49928a14c416f01fbb2719c88c9ba083f132a9