Feature/eli 702 code signing enable in prod #3492
eddalmond1cicd-1-pull-request.yaml
on: pull_request
Set CI/CD metadata
6s
Commit stage
/
Scan secrets
11s
Commit stage
/
Check file format
8s
Commit stage
/
Check Markdown format
7s
Commit stage
/
Check English usage
10s
Commit stage
/
Lint Terraform
6s
Commit stage
/
Checkov Terraform
41s
Commit stage
/
Count lines of code
9s
Commit stage
/
Scan dependencies
50s
Commit stage
/
OWASP Dependency Scan
35s
Commit stage
/
Check for dead code
31s
Acceptance stage
/
Contract test
5s
Acceptance stage
/
Security test
6s
Acceptance stage
/
UI test
6s
Acceptance stage
/
UI performance test
6s
Acceptance stage
/
Integration test
2m 22s
Acceptance stage
/
Accessibility test
4s
Acceptance stage
/
Load test
4s
Acceptance stage
/
Environment tear down
3s
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.26 KB |
sha256:1cd324271f8dd113e70c7d6eadf28de25d5a532431681e8dbcfb79552083f4f3
|
|
|
integration-test-results
|
2.33 KB |
sha256:f77fa1239414e20365bd31344511e6653025622af5c2092e3dca1cd010470203
|
|
|
lambda
|
19.2 MB |
sha256:b114ad3cd3e744a369db3629187f3ce0201638ed2b29b6a3a3f7e5fb7f6c5145
|
|
|
lines-of-code-report-.json.zip
|
844 Bytes |
sha256:9b913ba37f55a3f9a5db04b4b4341e4d93837ea743378b8d0c69d41fa1dfab80
|
|
|
sbom-repository-report.json.zip
|
58.7 KB |
sha256:43851083204b3934bf6c8545176ee60e1fca4acd52e7f2dd4a7c0855943af4af
|
|
|
vulnerabilities-repository-report-.json.zip
|
4.6 KB |
sha256:d1afd926d39081c5457b3ffb2553b5e3889990629f889d6e545fcce868da1537
|
|