Skip to content

CCM-17397: Update mesh-poll timeout buffer #2629

CCM-17397: Update mesh-poll timeout buffer

CCM-17397: Update mesh-poll timeout buffer #2629

Triggered via push April 27, 2026 10:58
Status Success
Total duration 6m 28s
Artifacts 7
Set CI/CD metadata
6s
Set CI/CD metadata
Commit stage  /  Scan secrets
12s
Commit stage / Scan secrets
Commit stage  /  Check file format
6s
Commit stage / Check file format
Commit stage  /  Check Markdown format
3s
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
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
54s
Commit stage / Scan dependencies
Commit stage  /  Detect Terraform Changes
5s
Commit stage / Detect Terraform Changes
Commit stage  /  Run terraform-docs
6s
Commit stage / Run terraform-docs
Commit stage  /  Lint Terraform
19s
Commit stage / Lint Terraform
Test stage  /  Contract tests
57s
Test stage / Contract tests
Test stage  /  Linting
2m 36s
Test stage / Linting
Test stage  /  Typecheck
2m 4s
Test stage / Typecheck
Test stage  /  Detect Schema Changes
5s
Test stage / Detect Schema Changes
Test stage  /  Unit tests
3m 45s
Test stage / Unit tests
Test stage  /  Check generated dependencies
0s
Test stage / Check generated dependencies
Test stage  /  Perform static analysis
1m 30s
Test stage / Perform static analysis
Build stage  /  Detect Documentation Changes
Build stage / Detect Documentation Changes
Build stage  /  Build Docs
Build stage / Build Docs
Trigger dynamic environment creation
0s
Trigger dynamic environment creation
Publish stage  /  Publish packages
Publish stage / Publish packages
Acceptance stage  /  Accessibility test
Acceptance stage / Accessibility test
Acceptance stage  /  Integration test
Acceptance stage / Integration test
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Fit to window
Zoom out
Zoom in

Annotations

14 warnings
Test stage / Detect Schema Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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 / Contract 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 / Linting: lambdas/ttl-handle-expiry-lambda/src/__tests__/app/dlq.test.ts#L183
Variable Assigned to Object Injection Sink
Test stage / Linting: src/typescript-schema-generator/src/generate-types.ts#L34
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: src/typescript-schema-generator/src/generate-guard-functions.ts#L51
Found writeFileSync from package "node:fs" with non literal argument at index 0
Test stage / Linting: utils/utils/src/event-publisher/event-publisher.ts#L101
Function Call Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L47
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/dynamodb/delete-dynamo-batch.ts#L34
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/config-reader.ts#L69
Variable Assigned to Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L52
Generic Object Injection Sink
Test stage / Linting: utils/utils/src/cache/cache.ts#L33
Variable Assigned to Object Injection Sink
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 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 / Perform static analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@634f93cb2916e3fdff6788551b99b062d0335ce0. 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
code-coverage-report
17.1 KB
sha256:804d380ad4bc48eac0f9858533b46701cffb5644bfcf74f7d66b06d0b9bcea7d
lines-of-code-report.json.zip
993 Bytes
sha256:a282da87de3d416075b4fb4e78b8b520a27117b64fedfc96e9536430af83c2d0
pact-contracts
609 Bytes
sha256:ffef9491c78159ba7e593b6b9218d6b337e268e1f7472e89da6c4fe8f229852e
python-coverage-reports
13.4 KB
sha256:5e84a9cc046b43aa4d1325bdbd80f6c2f67b2b96ef66915e8874dea5d5f93442
sbom-repository-report.json.zip
376 KB
sha256:e556fbbec6409d8b6b67501bd7571be50c322d6acca17be1e4e3d17060287f03
unit-tests
1.97 MB
sha256:83e73d7516c315fece35751d43e9a5a2bd6d8a408ededa0b75b211f29c634b36
vulnerabilities-repository-report.json.zip
4.44 KB
sha256:d8d27dee11564d17883411ca87e6d892e69a7d441ed5b51d2180eef817700019