[ELI-702] adding required boundry widening #3397
TOEL2cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
4s
Commit stage
/
Scan secrets
9s
Commit stage
/
Check file format
8s
Commit stage
/
Check Markdown format
4s
Commit stage
/
Check English usage
6s
Commit stage
/
Lint Terraform
8s
Commit stage
/
Checkov Terraform
36s
Commit stage
/
Count lines of code
5s
Commit stage
/
Scan dependencies
42s
Commit stage
/
OWASP Dependency Scan
32s
Commit stage
/
Check for dead code
41s
Acceptance stage
/
Contract test
4s
Acceptance stage
/
Security test
3s
Acceptance stage
/
UI test
6s
Acceptance stage
/
UI performance test
6s
Acceptance stage
/
Integration test
2m 46s
Acceptance stage
/
Accessibility test
6s
Acceptance stage
/
Load test
4s
Acceptance stage
/
Environment tear down
4s
Annotations
5 warnings
|
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 / OWASP Dependency Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: github/codeql-action/upload-sarif@v3. 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 / OWASP Dependency Scan
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
|
|
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/
|
|
Acceptance stage / Integration test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: phoenix-actions/test-reporting@v15. 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 | |
|---|---|---|---|
|
coverage.xml
|
7.23 KB |
sha256:f39120487407aeb58170a4d1cdc8dd207a43ddfa96a2b5a89a56fb2d6d1551f2
|
|
|
integration-test-results
|
2.33 KB |
sha256:ad7175b0fc475f6deddd389bada976e4ead60ec7344b3f866d87bfc4c6fc311e
|
|
|
lambda
|
19.1 MB |
sha256:5149b7086fac281f0f911f81568e18e15ca87d9de15a15a5e98f2ccab9a5ce8b
|
|
|
lines-of-code-report-.json.zip
Expired
|
839 Bytes |
sha256:c350c835ed6a9abe6b247b7d16901cb004ccba1787516e7df4f90342c5365cea
|
|
|
sbom-repository-report.json.zip
Expired
|
59.7 KB |
sha256:d82793b3a7b490187473a9efc2a7cebf3319ebb5642faff64e30c3577b3849d6
|
|
|
vulnerabilities-repository-report-.json.zip
Expired
|
4.01 KB |
sha256:031b0042a546ceed77e8688552d41cefc391b6a04622734982ae997e2c34df8c
|
|