Skip to content

eli-759 - adding permissions to the regression test calls #3481

eli-759 - adding permissions to the regression test calls

eli-759 - adding permissions to the regression test calls #3481

Triggered via pull request April 24, 2026 08:52
Status Success
Total duration 7m 18s
Artifacts 6

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
7s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Markdown format
7s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
6s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
10s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
32s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
8s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
42s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
41s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
34s
Commit stage / Check for dead code
Test stage  /  Linting
36s
Test stage / Linting
Test stage  /  Unit tests
55s
Test stage / Unit tests
Test stage  /  Perform static analysis
52s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
1m 45s
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
6s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
4s
Acceptance stage / Contract test
Acceptance stage  /  Security test
3s
Acceptance stage / Security test
Acceptance stage  /  UI test
4s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
4s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
2m 25s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
3s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
4s
Acceptance stage / Load test
Acceptance stage  /  Environment tear down
4s
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

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.28 KB
sha256:e736d978a00d15007fd24e8dde709b7a9e9a8fe603374826a9812b6118b21be4
integration-test-results
2.32 KB
sha256:7725bbefc335a80e36342c04fc9c958a4bb5a23076a90ccf94cd5934f59c9553
lambda
19.2 MB
sha256:383dc9a441b52652ea2b139e725cd645231648f0c19f662e685041302a83d385
lines-of-code-report-.json.zip
842 Bytes
sha256:51616a348c0ec0b77c1dcd5c715841c12a30ae0f4a60a128b8d3997f964168e7
sbom-repository-report.json.zip
58.6 KB
sha256:68c7946d501ca5154cb1d88a58cb07db5dfbbedec46355a11b24be3f6a814888
vulnerabilities-repository-report-.json.zip
4.61 KB
sha256:61c5431883a640962ed9957f1bfcc3f97ba58fda0b92303f59ed83f240a0a446