CCM-16553: disable console log for utility tool #2605
cicd-1-pull-request.yaml
on: push
Set CI/CD metadata
5s
Commit stage
/
Scan secrets
18s
Commit stage
/
Check file format
4s
Commit stage
/
Check Markdown format
5s
Commit stage
/
Check English usage
10s
Commit stage
/
Check TODO usage
6s
Commit stage
/
Count lines of code
10s
Commit stage
/
Scan dependencies
58s
Commit stage
/
Run terraform-docs
Commit stage
/
Lint Terraform
Test stage
/
Contract tests
43s
Test stage
/
Linting
2m 37s
Test stage
/
Typecheck
2m 10s
Publish stage
/
Publish packages
Acceptance stage
/
Security test
6s
Acceptance stage
/
UI test
4s
Acceptance stage
/
UI performance test
6s
Acceptance stage
/
Integration test
11m 24s
Acceptance stage
/
Accessibility test
4s
Acceptance stage
/
Load test
9s
Annotations
1 error and 15 warnings
|
Acceptance stage / Integration test
Process completed with exit code 1.
|
|
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:
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/event-publisher/event-publisher.ts#L99
Generic 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 / Linting:
scripts/nft-event-generator/src/utils/csv-reader.ts#L10
Found readFileSync from package "node:fs" with non literal argument at index 0
|
|
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/
|
|
Build stage / Detect Documentation 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
code-coverage-report
|
17 KB |
sha256:47c73ac1e30a372b8ad2d6030168748e9affdd92a3da2da5a041f368b963f039
|
|
|
lines-of-code-report.json.zip
|
985 Bytes |
sha256:8d83c2ab135f95cc091fe943319143677a428b3f77c6924a9640d7d83355b602
|
|
|
pact-contracts
|
609 Bytes |
sha256:5b65956d5028ba01f2eb178be58cbd987b08dec2229634e9ec3dcf6fbc030c05
|
|
|
python-coverage-reports
|
13.4 KB |
sha256:b17c6330d729a7b16e742b19501e8d29bffc1224c2fad574cb3e982d139ee785
|
|
|
sbom-repository-report.json.zip
|
393 KB |
sha256:4f60213765488d0422e0d77e5c461f80b1b30f5e43f895cece597c040fdb42aa
|
|
|
unit-tests
|
1.95 MB |
sha256:b96e14117e09d4a9eeef1cdf1d00e5f6f17718a531cb6689086526fccd362766
|
|
|
vulnerabilities-repository-report.json.zip
|
15.4 KB |
sha256:b07439302c7e5c62f21ad8b5f0f9728a89eb7b4f3f8a0a54c560a1ab2c6b63bf
|
|