Skip to content

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

eli-759 - adding permissions to the regression test calls

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

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

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
4s
Set CI/CD metadata
Commit stage  /  Scan secrets
9s
Commit stage / Scan secrets
Commit stage  /  Check file format
7s
Commit stage / Check file format
Commit stage  /  Check Markdown format
7s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
9s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
7s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
33s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
13s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
43s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
33s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
32s
Commit stage / Check for dead code
Test stage  /  Linting
37s
Test stage / Linting
Test stage  /  Unit tests
52s
Test stage / Unit tests
Test stage  /  Perform static analysis
45s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
1m 46s
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
4s
Acceptance stage / Environment set up
Acceptance stage  /  Contract test
6s
Acceptance stage / Contract test
Acceptance stage  /  Security test
6s
Acceptance stage / Security test
Acceptance stage  /  UI test
6s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
4s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
2m 44s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
3s
Acceptance stage / Accessibility test
Acceptance stage  /  Load test
3s
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.31 KB
sha256:b83400adf3d6e59438713ea5282f5ae828b6f5eddb51b421d989c279686834bb
integration-test-results
2.34 KB
sha256:64c881e5ce53d39ea17c81cf66efb629ac46b0e79aa927fd8ebd7027d6142ddf
lambda
19.2 MB
sha256:c6f096e59fedc879d1fdf8ea1512009a5424106bf6af8f71193da9c39dd62efd
lines-of-code-report-.json.zip
841 Bytes
sha256:5954c5b7a6a98dcaa2b9945bcedc66210a9fcf11644d64a74d318eed5d554e13
sbom-repository-report.json.zip
58.6 KB
sha256:2b1ee7f6ebf4a2793699ac71bdffd50b5f144ef6d442b913841a5ef08a38ee82
vulnerabilities-repository-report-.json.zip
4.61 KB
sha256:2a966f7ba8e78960448c6698dc5988083b8fe1f646c49152733a4773544683e6