New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
breaking changes in 1.5.2 and 1.5.3 - InvalidManifestError #83
Comments
From my point of view this is a breaking change and should not be introduced without a major (or at least minor) version and a note in the Release info. I am using your hooks everywhere and managing the upgrade with renovate (as many others). |
for people looking for a solution: upgrade to pre-commit latest version (currently 3.3.3) and it will work. On Arch I am not able to switch to the 3.3.3 version natively, instead (as a quickfix) I use nix to bypass the aur packaging system (use channel unstable) |
Thank you for reporting this @tyriis 👍
The new The This means that this hook since v1.5.2 must be used with |
More information on the issue this is working around: Lucas-C/pre-commit-hooks#83
More information on the issue this is working around: Lucas-C/pre-commit-hooks#83
# Argilla Community Growers Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged. # Pull Request Templates Please go the the `Preview` tab and select the appropriate sub-template: * [🐞-bug](?expand=1&template=bug.md) * [📚-documentation](?expand=1&template=docs.md) * [🆕-features](?expand=1&template=features.md) I tried to select "bug", but it didn't work for me ... maybe too tired. # Generic Pull Request Template I created a new conda env with the `environment_dev.yml` and encountered [this issue](Lucas-C/pre-commit-hooks#83). Bumping up the pre-commit version fixes it. Closes #<issue_number> **Type of change** (Please delete options that are not relevant. Remember to title the PR according to the type of change) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (change restructuring the codebase without changing functionality) - [ ] Improvement (change adding some improvement to an existing functionality) - [ ] Documentation update **How Has This Been Tested** (Please describe the tests that you ran to verify your changes. And ideally, reference `tests`) - [ ] Test A - [ ] Test B **Checklist** - [ ] I added relevant documentation - [ ] follows the style guidelines of this project - [ ] I did a self-review of my code - [ ] I made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I filled out [the contributor form](https://tally.so/r/n9XrxK) (see text above) - [ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
More information on the issue this is working around: Lucas-C/pre-commit-hooks#83
More information on the issue this is working around: Lucas-C/pre-commit-hooks#83
It seem that something is not working as expected in the latest version
error information
It seems, that version constraint check is not working as it should, but I am sure it is not related to the hook but to the framework.
The text was updated successfully, but these errors were encountered: