Repository navigation
fix(deps): keep library dependency ranges and requires-python out of Renovate pins - #15
Merged
Merged
Conversation
ExtraToast
added
type: bug
This file contains hidden or 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
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.
What changed
Renovate's shared preset pins every range. In this library that rewrote
requires-pythonto==3.15.2andcryptography>=44to==50.0.2(PR #6), which makes the lockfile update fail (renovate/artifacts) and would force consumers onto one interpreter and one cryptography release.requires-pythonis no longer touchedHow it was checked
The rule set was read against the Renovate pep621 manager's dep types (
project.dependencies,requires-python). The effect shows on the next Renovate run, which should recreate #6 with only the hatchling pin.