Bump hashicorp/terraform from 1.9.4 to 1.9.5 (#562) #1262
wcmjuniorAnnotations
3 warnings
|
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3, actions/setup-python@v2, pre-commit/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
lint
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/heads/main, Key: pre-commit-2-080a6d4be4b75c26102b3bb03053320ce110229aa06b43441ffb4965cd0d067e-1d1e0ff9aa55beb0dac8743d0814259bb12e8f4280e4fc320e67e850f83f09f3, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f
This only has performance implications and won't change the result of your pre-commit tests.
If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'.
For example try to run 'pre-commit autoupdate' or simply add a blank line.
This will result in a different hash value and thus a different cache target.
|