Repository navigation
dependabot: raise a pip floor only when the range no longer covers the release - #81
Merged
Merged
Conversation
…e release The lower bounds in pyproject.toml are the oldest versions the package supports. The "Dependency floor audit" job resolves exactly those floors (--resolution lowest-direct, on every supported Python) and runs pip-audit on them. Dependabot's default strategy turned every ">=" floor into a PR that raised it to the newest release, which locks users out for no reason. increase-if-necessary raises a floor only when a new version falls outside the declared range, so the floors stay the oldest supported versions and the audit stays meaningful. A floor that is vulnerable or no longer installs is still caught by the audit and raised by hand. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 26, 2026
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.
The lower bounds in
pyproject.tomlare the oldest versions this package supports, not the newest it was tested with. The "Dependency floor audit" job intest-jvm.ymlresolves exactly those floors (--resolution lowest-direct, on every supported Python) and runspip-auditon them, so a floor that is too old or vulnerable fails CI.Dependabot's default strategy turned every
>=floor into a PR that raised it to the newest release (numpy>=2.4.6, polars>=2.0.0, jpype1>=1.7.1, pyarrow>=26.0.0, redis>=8.1.0, and so on). That locks users out of older environments for no reason, and it would leave the floor audit checking the newest versions instead of the oldest.This sets
versioning-strategy: increase-if-necessaryon the pip block. Dependabot then raises a floor only when a new release falls outside the declared range. A floor that is vulnerable or no longer installs is still caught by the floor audit and raised by hand, with the reason written beside it inpyproject.toml(as for setuptools). Thegithub-actionsblock is unchanged.Checked locally: the file validates against the Dependabot schema (
check-jsonschema --builtin-schema vendor.dependabot),yamllintis clean, andactionlintis clean on all workflows.Once this is merged, the open pip floor PRs (#55, #56, #58 to #65) are closed with a pointer here.
🤖 Generated with Claude Code