Skip to content

CCM-15594: Use proxygen ptl or prod secrets #4386

CCM-15594: Use proxygen ptl or prod secrets

CCM-15594: Use proxygen ptl or prod secrets #4386

Triggered via pull request April 30, 2026 13:17
Status Failure
Total duration 25m 11s
Artifacts 15

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
41s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
9s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
13s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
8s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
24s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
52s
Commit stage / Scan dependencies
Commit stage  /  Check for changes to event schema package compared to main branch
6s
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
53s
Test stage / Check generated dependencies
Test stage  /  Pact tests
1m 1s
Test stage / Pact tests
Test stage  /  Linting
3m 14s
Test stage / Linting
Test stage  /  Typecheck
1m 57s
Test stage / Typecheck
Test stage  /  Unit tests
2m 59s
Test stage / Unit tests
Test stage  /  Test coverage
6s
Test stage / Test coverage
Test stage  /  Perform static analysis
1m 4s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 56s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
7m 40s
Build stage / Create Dynamic Environment
Matrix: Build stage / Build OAS spec for main
Build stage  /  Build OAS spec for sandbox
1m 1s
Build stage / Build OAS spec for sandbox
Build stage  /  Build OAS spec for PR
48s
Build stage / Build OAS spec for PR
Build stage  /  Populate Supplier Config
50s
Build stage / Populate Supplier Config
Build stage  /  OAS spec ready
5s
Build stage / OAS spec ready
Build stage  /  Build proxies
0s
Build stage / Build proxies
Build stage  /  Build SDKs
1m 32s
Build stage / Build SDKs
Acceptance stage  /  Run Acceptance Tests
10m 27s
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

1 error and 33 warnings
Acceptance stage / Run Acceptance Tests
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>0LljzaQAAAADAgqiWAMvVQrSNWp7PcAOHTVNQMzExMDAwMTA0MDUzAEVkZ2U=
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 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 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-20260430.131813+ed29719
20.7 KB
sha256:9a454d370ab7528ec1369242d9e6202d11b36f0cc10b00c354676305fb869984
api-oas-specification-internal-dev-sandbox-1.1.6-20260430.131813+ed29719
20.9 KB
sha256:10bfd9771487aea53435152b45503666d08bae6aae97f8eb3ee27366c313ea8b
code-coverage-report
4.58 KB
sha256:db689604308b05cbcaeb54d41179bbba2935c330efc990be1017dceba3fe5772
jekyll-docs-1.1.6-20260430.131813+ed29719
1.4 MB
sha256:7c898f66086a8622a64cd3de67137a5e5e160d2aa8d2c44e72e0ac79cc47d5db
lines-of-code-report.json.zip
971 Bytes
sha256:590956c9f8105bf0a3a029c2f7b5a124941cab2437af0355a2a58269ec5ec249
sbom-repository-report.json.zip
150 KB
sha256:954449936be294225ef2f71c1ce3b7685773a310509b5067efc4631b6fea1cc9
sdk-csharp-1.1.6-20260430.131813+ed29719
1020 KB
sha256:9e10aeb8fda6cf3c76b92068fe3c30c4b33fe5fa481af1c441236b63511eaae9
sdk-html-1.1.6-20260430.131813+ed29719
8.54 KB
sha256:d8057c331b3c5cb243c5117373601c83081b53177f929507b59081c35f81062b
sdk-html-docs-1.1.6-20260430.131813+ed29719
9.31 KB
sha256:8357b77c029252cc6611c68e8b842c0fd5de84969cc0d98c26ad31fdf13c0b22
sdk-python-1.1.6-20260430.131813+ed29719
223 KB
sha256:0d3933a7d235d8e3fbff0c044beb473a63c26515063327f670e6ae977e97f065
sdk-swagger-1.1.6-20260430.131813+ed29719
1.09 MB
sha256:d07eaab359a4e83e013857bb57665a3620cc0a5520b41786208ba84e15592445
sdk-swagger-docs-1.1.6-20260430.131813+ed29719
1.09 MB
sha256:d821fa434205b8e3f69a254e2e6c4ed7accbde86eb96a528871f35697f453bb2
sdk-ts-1.1.6-20260430.131813+ed29719
98.8 KB
sha256:15219fd26781ab3af7476ece8a00169f26ee0ecbb457a9ac1ee73c9ca55cbd37
unit-tests
839 KB
sha256:e0d364096204cc65482ba6824c9ad74f24bcf0d1014ac25356bc4ab81f1bb88c
vulnerabilities-repository-report.json.zip
20.2 KB
sha256:5d0ddfc953cfb1c695782c0ada4165d38b923122cfa69698e3345a285a391a72