Align the core constraint with the rest of the ecosystem - #2
Merged
Conversation
rtk shipped v0.14.0 on a floating range while all 14 sibling packages use a caret. That made it the only package that would resolve against a future core minor it had never been tested with.
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
1 participant
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.
rtk v0.14.0 went out on
>=0.14 <1.0, released before the ecosystem settled on caret. Every other package is on^0.14, so rtk is currently the only one that would float onto core 0.15+ untested.Constraint-only change. Ships as v0.14.1, since v0.14.0 is already published.