Skip to content

feature/CCM-12185 Add new endpoint to get mi information #3967

feature/CCM-12185 Add new endpoint to get mi information

feature/CCM-12185 Add new endpoint to get mi information #3967

Triggered via pull request April 7, 2026 11:01
Status Failure
Total duration 1m 28s
Artifacts 3

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
21s
Commit stage / Scan secrets
Commit stage  /  Check file format
12s
Commit stage / Check file format
Commit stage  /  Check Markdown format
7s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
13s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
4s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
12s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 16s
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
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
Test stage / Check generated dependencies
Test stage  /  Linting
Test stage / Linting
Test stage  /  Pact tests
Test stage / Pact tests
Test stage  /  Typecheck
Test stage / Typecheck
Test stage  /  Unit tests
Test stage / Unit tests
Test stage  /  Perform static analysis
Test stage / Perform static analysis
Test stage  /  Test coverage
Test stage / Test coverage
Build stage  /  Build Docs
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
Build stage / Create Dynamic Environment
Matrix: Build stage / artefact-oas-spec
Waiting for pending jobs
Build stage  /  Build OAS spec for sandbox
Build stage / Build OAS spec for sandbox
Build stage  /  Build SDKs
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

2 errors and 3 warnings
Commit stage / Check TODO usage
Process completed with exit code 1.
Commit stage / Check file format
Process completed with exit code 1.
Commit stage / Check for changes to event schema package compared to main branch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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 / 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/

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip
968 Bytes
sha256:0ee718653ff5dcab62a4ef201fd8e3c6faa1479be2ca9c0278b432528708ae00
sbom-repository-report.json.zip
148 KB
sha256:b5a4ec6ae34625e14a5baf3d661d0457ca08e432a12baac56e04b5eb36a870ae
vulnerabilities-repository-report.json.zip
13.9 KB
sha256:e2e8325541da2023867d78124a4babcad1aa89a036c310c43b639581b5c98766