[pre-commit.ci] pre-commit autoupdate #217
Annotations
1 error and 3 warnings
Run pre-commit/[email protected]
The process '/opt/hostedtoolcache/Python/3.12.1/x64/bin/pre-commit' failed with exit code 1
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/[email protected], actions/setup-python@v3, actions/[email protected], pre-commit/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
|
Run pre-commit/[email protected]
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/pull/169/merge, Key: pre-commit-2-7620fca0ce1d0792718f844191a34dab987ec12be895d325c2fce8722fe77932-94dd1c58e04a6290a06791d3df888d24279230ef1e3f55fd0579782f167e4e0a, 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.
|
The logs for this run have expired and are no longer available.
Loading