Skip to content

CCM-14318: Endpoints fetching letters return 500 instead of 404 when letter not found for supplier #3716

CCM-14318: Endpoints fetching letters return 500 instead of 404 when letter not found for supplier

CCM-14318: Endpoints fetching letters return 500 instead of 404 when letter not found for supplier #3716

Triggered via pull request March 24, 2026 12:56
Status Failure
Total duration 16m 14s
Artifacts 7

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
12s
Commit stage / Scan secrets
Commit stage  /  Check file format
5s
Commit stage / Check file format
Commit stage  /  Check Markdown format
7s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
8s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
4s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
7s
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
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
0s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
50s
Test stage / Check generated dependencies
Test stage  /  Pact tests
1m 2s
Test stage / Pact tests
Test stage  /  Linting
2m 52s
Test stage / Linting
Test stage  /  Typecheck
1m 54s
Test stage / Typecheck
Test stage  /  Unit tests
3m 8s
Test stage / Unit tests
Test stage  /  Test coverage
6s
Test stage / Test coverage
Test stage  /  Perform static analysis
58s
Test stage / Perform static analysis
Build stage  /  Build Docs
1m 32s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
6m 26s
Build stage / Create Dynamic Environment
Matrix: Build stage / artefact-oas-spec
Build stage  /  Build OAS spec for sandbox
1m 2s
Build stage / Build OAS spec for sandbox
Build stage  /  Build SDKs
0s
Build stage / Build SDKs
Build stage  /  Build proxies
Build stage / Build proxies
Acceptance stage  /  Run Acceptance Tests
4m 24s
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 30 warnings
Acceptance stage / Run Acceptance Tests
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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 / Linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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#L78
Variable Assigned to Object Injection Sink
Test stage / Linting
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@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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']
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/checkout@v4, actions/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, ruby/setup-ruby@v1.180.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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>0iYvCaQAAAABn8m7MolwyS7Yp+iSIscPURE0yRURHRTEwMjIARWRnZQ==
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@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sandbox-1.1.5-20260324.125700+eab1dfc
20.9 KB
sha256:2d43d9f662c35c2e7bf72e8e6d026f2139563950d0a1d25e1a8adef4ba099581
code-coverage-report
4.26 KB
sha256:6fb6c16f3a290e920187503149f6929919a51ad010298d74f4bb5f46fe79eab3
jekyll-docs-1.1.5-20260324.125700+eab1dfc Expired
1.4 MB
sha256:b8b6fcd2bdc8c9bb55a4ae31f4f9facfc47faf6ec69f0c518a33f4f02f0d386b
lines-of-code-report.json.zip Expired
963 Bytes
sha256:aea4628e22d73e8128d1e7ac9f4e8fa26a8d5ae16d36a3b6ec9a7692769ad4f8
sbom-repository-report.json.zip Expired
153 KB
sha256:5c40d7a48c21e915c1d3dcea387d3f923050e5cbef2bd9751c6885762f9ad760
unit-tests
811 KB
sha256:dc30e90d570878811280aa6b86305878dfe12835baa46948b4d016314e756da6
vulnerabilities-repository-report.json.zip Expired
5.36 KB
sha256:b931db8bb4ff8ccb36a2d23d3db59327db96d0486d5252cc539fc34d69f6f170