Skip to content

fixing release candidate workflow by adding proxygen TF_VAR #3202

fixing release candidate workflow by adding proxygen TF_VAR

fixing release candidate workflow by adding proxygen TF_VAR #3202

Triggered via pull request March 11, 2026 16:15
Status Success
Total duration 7m 40s
Artifacts 6

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
8s
Set CI/CD metadata
Commit stage  /  Scan secrets
16s
Commit stage / Scan secrets
Commit stage  /  Check file format
8s
Commit stage / Check file format
Commit stage  /  Check Markdown format
4s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
10s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
6s
Commit stage / Lint Terraform
Commit stage  /  Checkov Terraform
33s
Commit stage / Checkov Terraform
Commit stage  /  Count lines of code
16s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
48s
Commit stage / Scan dependencies
Commit stage  /  OWASP Dependency Scan
37s
Commit stage / OWASP Dependency Scan
Commit stage  /  Check for dead code
36s
Commit stage / Check for dead code
Test stage  /  Linting
36s
Test stage / Linting
Test stage  /  Unit tests
57s
Test stage / Unit tests
Test stage  /  Perform static analysis
56s
Test stage / Perform static analysis
Build stage  /  Lambda Artefact
1m 40s
Build stage / Lambda Artefact
Acceptance stage  /  Environment set up
3s
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
4s
Acceptance stage / UI test
Acceptance stage  /  UI performance test
4s
Acceptance stage / UI performance test
Acceptance stage  /  Integration test
2m 35s
Acceptance stage / Integration test
Acceptance stage  /  Accessibility test
6s
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. 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. 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. 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. 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.14 KB
sha256:a04fde0578d944760cc88c2b738adaf33e2af5ef35d6719d943300fbaca5430d
integration-test-results
2.31 KB
sha256:4c9f185e47a5c1c9ae1501f68cd85b5d5cde76c46be224592efc38a50539a74c
lambda
18.9 MB
sha256:31a34a039fc378121b937b4f36cbb4177b40d47d4699f2ac01f3a345ae2fb597
lines-of-code-report-.json.zip Expired
845 Bytes
sha256:01887547707f8c9389abd852fa5f1583acc80360d67e1987b2a6b26a45051a39
sbom-repository-report.json.zip Expired
58.6 KB
sha256:d781dfccbc69e4b2a3924c2d814b4f687919366d105664e459ed40ba987861d4
vulnerabilities-repository-report-.json.zip Expired
3.01 KB
sha256:a0ba6a87f366466cecc2be651d1a658d80241b653f41bda7bee48c0f8042ccdc