The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/[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 uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/[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 uses node12 which is deprecated and will be forced to run on node16: actions/[email protected], 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/

There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/13/merge, Key: pre-commit-2-7620fca0ce1d0792718f844191a34dab987ec12be895d325c2fce8722fe77932-8b47dea5f26ffeaf0adeb521c7a1526e585afd550949dd7c11fa1f2e8fc2627b, 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.