Audit the version update behavior across ecosystems #10187
Labels
Ecosystems
Used by the maintainer team for internal-facing project tracking
Epic
L: git:submodules
Git submodules
L: python
There are a variety of issues that have been raised indicating inconsistencies with the version update behavior. For example, this issue for pip, which has triggered a potential fix, but it's unclear if this is the right way to handle this, given the long precedent of existing behavior that users rely on.
Instead of making a one-off fix for pip that may result in even more inconsistencies, we instead should undertake an audit of the version update behavior across ecosystems. This will give us a better view into how these options are working across the board, before deciding what (if any) changes we should make to the existing behavior.
Some recent pertinent issues, feel free to link more:
widen
strategy for Python #6630increase
strategy should move ranges forward, not widen them #6631increase
does not raise lower version in range #6519The text was updated successfully, but these errors were encountered: