Explicitly use pre-commit 3.6 #177
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Saying >= 3.5 or newer sounds great at first, but actually it makes it hard to know what pre-commit version we actually use. The lock file pins to the latest version greater 3.5 at whatever time the lock was created. Thus, we pin pre-commit, but to know what we pin it to, one has to look into the longish lock file whereas one would expect the information in the pyprojects.toml file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Saying >= 3.5 or newer sounds great at first, but actually it makes it hard to know what pre-commit version we actually use. The lock file pins to the latest version greater 3.5 at whatever time the lock was created. Thus, we pin pre-commit, but to know what we pin it to, one has to look into the longish lock file whereas one would expect the information in the pyprojects.toml file.