Merge pull request #14 from flyingcircusio/PL-132849-rewrite-rootdisk… #29
Annotations
3 warnings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/
|
Run pre-commit/[email protected]
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/heads/master, Key: pre-commit-2-2ce57c724eb4fbd4e8c5b67f21fd5e05841d89d4ce55413641423e33f080dd34-e3cf44ffae470627db069ace972e1cb363e3564ea1a065811929da91831bb479, 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.
|
Loading