Skip to content

Bump hashicorp/setup-terraform from 3.1.2 to 4.0.0 #1678

Bump hashicorp/setup-terraform from 3.1.2 to 4.0.0

Bump hashicorp/setup-terraform from 3.1.2 to 4.0.0 #1678

Triggered via pull request March 10, 2026 15:33
Status Cancelled
Total duration 2m 17s
Artifacts 3

cicd-1-pull-request.yaml

on: pull_request
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
8s
Commit stage / Scan secrets
Commit stage  /  Check file format
2m 3s
Commit stage / Check file format
Commit stage  /  Check Python format
11s
Commit stage / Check Python format
Commit stage  /  Check Markdown format
6s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
14s
Commit stage / Check English usage
Commit stage  /  Lint Terraform
18s
Commit stage / Lint Terraform
Commit stage  /  Count lines of code
9s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
50s
Commit stage / Scan dependencies
Test stage  /  Create coverage artefact name
Test stage / Create coverage artefact name
Test stage  /  Acceptance tests
Test stage / Acceptance tests
Test stage  /  Contract tests
Test stage / Contract tests
Test stage  /  Integration tests
Test stage / Integration tests
Test stage  /  Schema validation tests
Test stage / Schema validation tests
Test stage  /  Unit tests
Test stage / Unit tests
Test stage  /  Merge test coverage
Test stage / Merge test coverage
Test stage  /  SonarCloud Analysis
Test stage / SonarCloud Analysis
Build stage  /  Artefact 1
Build stage / Artefact 1
Build stage  /  Artefact 2
Build stage / Artefact 2
Acceptance stage  /  Environment set up
Acceptance stage / Environment set up
Acceptance stage  /  Load test
Acceptance stage / Load test
Acceptance stage  /  Security test
Acceptance stage / Security test
Acceptance stage  /  UI performance test
Acceptance stage / UI performance test
Acceptance stage  /  UI test
Acceptance stage / UI test
Acceptance stage  /  Environment tear down
Acceptance stage / Environment tear down
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
Commit stage / Check file format
The job has exceeded the maximum execution time of 2m0s
Commit stage / Check file format
The operation was canceled.
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 / Check Python format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. 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 / 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/

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip Expired
863 Bytes
sha256:98cd9e1f44891f99cbd8f86564011d78b74ce2d1e33f8b50af89aefd6152fc4e
sbom-repository-report.json.zip Expired
42.1 KB
sha256:6bc3e790851030209778d0d0790563e00a28b0d3c1d2f28ef09e474866511a11
vulnerabilities-repository-report.json.zip Expired
2.38 KB
sha256:30ede75d65a8ad7e564f9b00ce910d5ca9dc922a06bae6f38c59f0ab5d8ac875