Skip to content

CCM-19310: update pageCount constraint with duplex and sides (#614) #4896

CCM-19310: update pageCount constraint with duplex and sides (#614)

CCM-19310: update pageCount constraint with duplex and sides (#614) #4896

Triggered via push June 10, 2026 14:20
Status Success
Total duration 22m 25s
Artifacts 20
Set CI/CD metadata
7s
Set CI/CD metadata
Commit stage  /  Scan secrets
19s
Commit stage / Scan secrets
Commit stage  /  Check file format
11s
Commit stage / Check file format
Commit stage  /  Check Markdown format
7s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
12s
Commit stage / Check English usage
Commit stage  /  Check TODO usage
8s
Commit stage / Check TODO usage
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
1m 1s
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
4s
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
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
0s
Commit stage / Lint Terraform
Test stage  /  Check generated dependencies
55s
Test stage / Check generated dependencies
Test stage  /  Pact tests
1m 7s
Test stage / Pact tests
Test stage  /  Linting
3m 27s
Test stage / Linting
Test stage  /  Typecheck
1m 47s
Test stage / Typecheck
Test stage  /  Unit tests
3m 15s
Test stage / Unit tests
Test stage  /  Test coverage
5s
Test stage / Test coverage
Test stage  /  Perform static analysis
1m 1s
Test stage / Perform static analysis
Build stage  /  Build Docs
2m 40s
Build stage / Build Docs
Build stage  /  Create Dynamic Environment
5m 48s
Build stage / Create Dynamic Environment
Matrix: Build stage / Build OAS spec for main
Build stage  /  Build OAS spec for sandbox
1m 5s
Build stage / Build OAS spec for sandbox
Build stage  /  Build OAS spec for PR
0s
Build stage / Build OAS spec for PR
Build stage  /  Populate Supplier Config
38s
Build stage / Populate Supplier Config
Build stage  /  OAS spec ready
3s
Build stage / OAS spec ready
Build stage  /  Build proxies
1m 20s
Build stage / Build proxies
Build stage  /  Build SDKs
1m 21s
Build stage / Build SDKs
Acceptance stage  /  Run Acceptance Tests
8m 42s
Acceptance stage / Run Acceptance Tests
Publish stage  /  Publish packages
17s
Publish stage / Publish packages
Publish stage  /  Publish npm packages to npm.pkg.github.com
18s
Publish stage / Publish npm packages to npm.pkg.github.com
Publish stage  /  Publish nuget packages to nuget.pkg.github.com
11s
Publish stage / Publish nuget packages to nuget.pkg.github.com
Matrix: Publish stage / publish-oas-specs
Publish stage  /  Success notification
4s
Publish stage / Success notification
Fit to window
Zoom out
Zoom in

Annotations

39 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']
Publish stage / Publish packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-release@0cb9c9b65d5d1901c1f53e5e66eaf4afd303e70e, actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. 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/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish packages
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (int)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. 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/
Publish stage / Publish OAS spec (int)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (prod)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. 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/
Publish stage / Publish OAS spec (prod)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (internal-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. 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/
Publish stage / Publish OAS spec (internal-dev)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Publish stage / Publish OAS spec (ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-release-asset@e8f9f06c4b078e705bd2ea027f0926603fc9b4d5. 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/
Publish stage / Publish OAS spec (ref)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size Digest
api-oas-specification-int-1.2.0-20260610.142043+cd6e693
20.9 KB
sha256:073757a9b4b106d8efa0534cdc6dbac794995ea9d2e6cbbe2bc95feb59f43a76
api-oas-specification-internal-dev-1.2.0-20260610.142043+cd6e693
21 KB
sha256:6028738a500715ec329f878dfb4da6fb8e6d903027e07aa503c051197b0b9092
api-oas-specification-internal-dev-pr-1.2.0-20260610.142043+cd6e693
20.7 KB
sha256:a15f61f611e84b4e9e12578976979a0366dd00cbbae36a105a6ed434899ab648
api-oas-specification-internal-dev-sandbox-1.2.0-20260610.142043+cd6e693
20.9 KB
sha256:42517f75959296952d9d16304b5c6ddba9b7af84107eb2a467ed6589bcdcf6c9
api-oas-specification-prod-1.2.0-20260610.142043+cd6e693
20.9 KB
sha256:b2fe48cc7dad24267296d104f3ca93a29881d70fd99311c1cb7925b44cee9c20
api-oas-specification-ref-1.2.0-20260610.142043+cd6e693
20.9 KB
sha256:9edb3a22b5d06d9ec1855078a0fa06e335384268e3c5488618b1f1a5649d0534
code-coverage-report
5.68 KB
sha256:5461048d66702278d3b87453f00cc534b431148b2a0fdaec75dc1377e3c9fbc5
internal-dev-build-output
21 KB
sha256:dc95ae0e1ee5de8f0079931084beff219c96f4be9d166924dffcbc085290f0c3
jekyll-docs-1.2.0-20260610.142043+cd6e693 Expired
1.4 MB
sha256:f3b25c12c4b6e3bb88ccb91d2790e671e061be4a935e48a513847c08bb58241c
lines-of-code-report.json.zip
970 Bytes
sha256:3cab8534712188684acc3fc4b2142fb3b790e33bcc13216dc4e736da673666c6
sbom-repository-report.json.zip
125 KB
sha256:408c239bc616b9443d2fd4caadd553c0b3aa8bb88ee22065e8c5ffa04bc08b63
sdk-csharp-1.2.0-20260610.142043+cd6e693
1 MB
sha256:54594280d124ccc14a3fcf13260b18f36cccb9ad9455d840bc48a630b207b4c0
sdk-html-1.2.0-20260610.142043+cd6e693
8.54 KB
sha256:3c22efe8aaddc8a5926bc4d729014b4425dba4f483e2589858b4d5ed219932ba
sdk-html-docs-1.2.0-20260610.142043+cd6e693 Expired
8.7 KB
sha256:8663464c70e7060dca9c7577d8d15866f1b710d3b99d0f03e73fe4bc48d21ccd
sdk-python-1.2.0-20260610.142043+cd6e693
223 KB
sha256:ea26d89538436157fe15c73e99594ff0574d46316e0ab87f5a6d0d853beb0a80
sdk-swagger-1.2.0-20260610.142043+cd6e693
1.09 MB
sha256:e2350a0211eecd0beb67422b2e2cc49497813cd3246a0793f3bc345c8c41b08e
sdk-swagger-docs-1.2.0-20260610.142043+cd6e693 Expired
1.09 MB
sha256:4d380cffaeff13b5b2a0bfd14d3e477cc84c9e259854e16cf64a8cb533a57a6e
sdk-ts-1.2.0-20260610.142043+cd6e693
98.8 KB
sha256:3d3b202b443b788b8bd23a1e37b957c585ad715cb2bb942d30c2a06671e3416f
unit-tests
949 KB
sha256:89ba189b8e94ace516be0e316ad531db2afcad0c451afe7272abdee03138f3da
vulnerabilities-repository-report.json.zip
6.67 KB
sha256:28890f84d317ba1693bdaf30430d230df533c728dfe48e629069b98dba9d6c98