Skip to content

Pip package

Pip package #70

Triggered via pull request March 2, 2024 03:55
Status Success
Total duration 35s
Artifacts

formatting.yml

on: pull_request
pre-commit
27s
pre-commit
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
pre-commit
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2, pre-commit/action@v2.0.3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
pre-commit
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/action@v2.0.3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
pre-commit
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/24/merge, Key: pre-commit-2-1e8cfed26beee61bc4b6848c6d922cb8622c7a3be7b7e9a08f6cb0e6c0718144-f65a5da87462cd74ee062033090ff8526c544cd03320f3e59af7729fa2c2eba1, 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.