Skip to content

CCM-15594: Add override to internal branch #4389

CCM-15594: Add override to internal branch

CCM-15594: Add override to internal branch #4389

Triggered via push May 1, 2026 08:46
Status Success
Total duration 17m 21s
Artifacts 15
Set CI/CD metadata
8s
Set CI/CD metadata
Commit stage  /  Scan secrets
37s
Commit stage / Scan secrets
Commit stage  /  Check file format
11s
Commit stage / Check file format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
5s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
47s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
8s
Commit stage / Check for changes to event schema package compared to main branch
Commit stage  /  Detect Terraform Changes
6s
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
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
58s
Test stage / Check generated dependencies
Test stage  /  Pact tests
1m 6s
Test stage / Pact tests
Test stage  /  Linting
3m 11s
Test stage / Linting
Test stage  /  Typecheck
1m 54s
Test stage / Typecheck
Test stage  /  Unit tests
2m 51s
Test stage / Unit tests
Test stage  /  Test coverage
4s
Test stage / Test coverage
Test stage  /  Perform static analysis
58s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 46s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
4m 55s
Build stage / Create Dynamic Environment
Matrix: Build stage / Build OAS spec for main
Build stage  /  Build OAS spec for sandbox
58s
Build stage / Build OAS spec for sandbox
Build stage  /  Build OAS spec for PR
1m 1s
Build stage / Build OAS spec for PR
Build stage  /  Populate Supplier Config
39s
Build stage / Populate Supplier Config
Build stage  /  OAS spec ready
3s
Build stage / OAS spec ready
Build stage  /  Build proxies
0s
Build stage / Build proxies
Build stage  /  Build SDKs
1m 18s
Build stage / Build SDKs
Acceptance stage  /  Run Acceptance Tests
6m 40s
Acceptance stage / Run Acceptance 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

33 warnings
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>0r2n0aQAAAABP6TtuYTHSS6wIE06K4hgnUEhYMzFFREdFMDYxOQBFZGdl
Build stage / Build Docs
Failed to restore: Cache service responded with 400
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 for 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 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-internal-dev-pr-1.1.6-20260501.084606+891d5d5
20.7 KB
sha256:748ead5ac882899be8deef0140810d6e5e0f56bef6bc25b20fb1fb5dfeaf9c2e
api-oas-specification-internal-dev-sandbox-1.1.6-20260501.084606+891d5d5
20.9 KB
sha256:1681f7acc83be9b70fb88a6970b815d81183c66c8bf4b5949d16cc24cccace57
code-coverage-report
4.58 KB
sha256:7992e537e499edbe0ff478db86d543ed6704654126af781b23f9c553340dfa10
jekyll-docs-1.1.6-20260501.084606+891d5d5
1.4 MB
sha256:dae3c2db77cd3d610bf47f767720a6ea5369fa337ff01fdaa855997ba36309d2
lines-of-code-report.json.zip
979 Bytes
sha256:e17a433e3efdb6382b1929dca0b8794677c8d1bf5cd12ccb45a74f02ac335d67
sbom-repository-report.json.zip
150 KB
sha256:54a378d075ff4da0d47c67a8d64f0748542bd74182ad90075b02f7d448d2a8e3
sdk-csharp-1.1.6-20260501.084606+891d5d5
1020 KB
sha256:df1fb45aa28eca459ea7c890a801fd0f1aed1977bb2aeb7fa24958d24efd7e49
sdk-html-1.1.6-20260501.084606+891d5d5
8.54 KB
sha256:7de7b38bbf1b227c4da642600685bd48bbccbef21b0ae9dd1f03c48d5e8f6b96
sdk-html-docs-1.1.6-20260501.084606+891d5d5
9.31 KB
sha256:c2943f6d1573584c6568d316b7f67e146323c934ef789572e13d3415a29ac27c
sdk-python-1.1.6-20260501.084606+891d5d5
223 KB
sha256:175265dbb7ac8fb64280bf63f0f89c4a5721203d0e0dbb8ccd160fe811decb5a
sdk-swagger-1.1.6-20260501.084606+891d5d5
1.09 MB
sha256:885f8ff2434f0d92493eddd6c7dd425c733329e2713e0ccd575fdbc6f0aa6921
sdk-swagger-docs-1.1.6-20260501.084606+891d5d5
1.09 MB
sha256:c5a133227e243dd4369dd868c2781fc089f583943cd17892d15076261ef28df6
sdk-ts-1.1.6-20260501.084606+891d5d5
98.8 KB
sha256:dc8e1172165e4d337194c19e25a8c345040632f2b09310b7649a9ad7572b9160
unit-tests
839 KB
sha256:8e43e43f04b80c150bd1e2e51750febbfd585a0e673b747d977a4db83f6e7661
vulnerabilities-repository-report.json.zip
20.2 KB
sha256:c3528c7eba149dc97f59a632c64feaaca32cb303269cea89a51c426aa103b239