Skip to content
Pre-commit checks

Fix CI #16

Sign in to view logs

Fix CI

Fix CI #16

Triggered via pull request November 8, 2023 15:16
@guibescosguibescos
reopened #4
fix-ci
Status Success
Total duration 5m 13s
Artifacts –

pre-commit.yaml

on: pull_request
pre-commit
5m 4s
pre-commit
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
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, actions-rs/toolchain@v1, 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
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
pre-commit
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
pre-commit
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
pre-commit
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
pre-commit
There was an error saving the pre-commit environments to cache: reserveCache failed: Cache already exists. Scope: refs/pull/4/merge, Key: pre-commit-2-25aed7715436a63b1d89838a1529caad0b1398257093bcafd3eb53a5d4746a71-26033a7b6623bd8566dc72b42078481c6cf09f8d5562cecb100d0647c6895863, 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.