Skip to content

CCM-18631: stabilise component tests #4759

CCM-18631: stabilise component tests

CCM-18631: stabilise component tests #4759

Triggered via pull request June 1, 2026 09:12
Status Success
Total duration 19m 27s
Artifacts 15

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
13s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
5s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
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
1m 2s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
4s
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
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
48s
Test stage / Check generated dependencies
Test stage  /  Pact tests
57s
Test stage / Pact tests
Test stage  /  Linting
3m 11s
Test stage / Linting
Test stage  /  Typecheck
1m 45s
Test stage / Typecheck
Test stage  /  Unit tests
2m 50s
Test stage / Unit tests
Test stage  /  Test coverage
4s
Test stage / Test coverage
Test stage  /  Perform static analysis
1m 0s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 37s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
6m 44s
Build stage / Create Dynamic Environment
Matrix: Build stage / Build OAS spec for main
Build stage  /  Build OAS spec for sandbox
59s
Build stage / Build OAS spec for sandbox
Build stage  /  Build OAS spec for PR
56s
Build stage / Build OAS spec for PR
Build stage  /  Populate Supplier Config
42s
Build stage / Populate Supplier Config
Build stage  /  OAS spec ready
2s
Build stage / OAS spec ready
Build stage  /  Build proxies
0s
Build stage / Build proxies
Build stage  /  Build SDKs
1m 46s
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

26 warnings
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
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
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
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
Unexpected input(s) 'node-version', valid inputs are ['GITHUB_TOKEN']
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
asyncapi-unused-components-schema Potentially unused components schema has been detected.
Test stage / Linting
asyncapi-unused-components-schema Potentially unused components schema has been detected.
Test stage / Linting
asyncapi-info-license Info object must have "license" object.
Test stage / Linting
asyncapi-info-contact Info object must have "contact" object.
Test stage / Linting
asyncapi-3-tags AsyncAPI document must have non-empty "tags" array.
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 16th, 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>0a04dagAAAAAxrR2PxjaxQpRfhBI7/IW6Q0hHRURHRTE3MTQARWRnZQ==
Build stage / Build Docs
Failed to restore: Cache service responded with 400
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 16th, 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 16th, 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 16th, 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-20260601.091228+2595516
20.7 KB
sha256:9939a8b048ddd2ebfcd1d4889869b79669a968150aec30da9f638adec0d30b69
api-oas-specification-internal-dev-sandbox-1.1.6-20260601.091228+2595516
20.9 KB
sha256:be3a1d916c74935d61e2c4d1cebcbf3ad8bdb586c6091efe9e23a4e8c2f21eb1
code-coverage-report
5.41 KB
sha256:618a3362d7e54062d8e7a2315e8623fb07e936ddcab0433245c8abd88e151bf4
jekyll-docs-1.1.6-20260601.091228+2595516 Expired
1.4 MB
sha256:9966c2b158021623e8ab266c85af971f38a2c5aa6438ad3e5746d249fadd1560
lines-of-code-report.json.zip Expired
967 Bytes
sha256:c619f1b68c027c200fb91f498dcb885b193854e1f501b05e7af64845da7a53d1
sbom-repository-report.json.zip Expired
127 KB
sha256:0d491ed3f5eb794e9d77fd50f8dbb1319e4c2ba6d396b833facdac514589669f
sdk-csharp-1.1.6-20260601.091228+2595516
1 MB
sha256:c258f1ed0c2ac337a6fcf6fc3cc5dd2974f3fb20a1c4b45fdb2c2bd58b40a0f0
sdk-html-1.1.6-20260601.091228+2595516
8.54 KB
sha256:751ecf88b18459a0752bfa4c2fc92321030b9d2aab565a0f78c8c1e33c650b06
sdk-html-docs-1.1.6-20260601.091228+2595516 Expired
9.22 KB
sha256:c85febc730fb04b792c1410ebd159c09b224370867a294dfbcbbc55ca201e717
sdk-python-1.1.6-20260601.091228+2595516
223 KB
sha256:3636013b413b56e6a0585b5ecf71314e06a7c65e078fa68b9d612fd6a2799117
sdk-swagger-1.1.6-20260601.091228+2595516
1.09 MB
sha256:f00c8f2892d2f6fef4313417eac945e9d201de81b4e6eab5763f03b09527e522
sdk-swagger-docs-1.1.6-20260601.091228+2595516 Expired
1.09 MB
sha256:c71a7c8f6bd1b50c1f894abf018c8ba2bdcefebd7178fc6ed2d402b43e792030
sdk-ts-1.1.6-20260601.091228+2595516
98.8 KB
sha256:79bc23a4199653db5355d12d322db1b40fdb2485efccc34d24d8e59f4de35546
unit-tests
894 KB
sha256:4066bbdb7cb4a616d908b4742016a70dfa213a9c9bb81843a2d2f19edcc83e8d
vulnerabilities-repository-report.json.zip Expired
5.99 KB
sha256:ac3e01aede079af07876e8d0d459dd3b19181b821b99e639869157a2a7ebf962