Teach update-dependency about more range specifiers and make it adopt the current range for any tag #7709
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.
References
Follows up on #7590 and fixes a bug there.
Code changes
Currently there is a special case to adopt the existing range specifier if the upgraded range is ‘latest’. This extends this special case for any upgrade to a tag version. This also allows for range specifiers of =, <, >, <=, and >=.
This fixes a bug where updating to ^latest generates a spec of ^^latest in the current version.
User-facing changes
Backwards-incompatible changes