Update changesets and depend on @keystar/ui in @keystatic/core with a ~ - #1610
Merged
Conversation
🦋 Changeset detectedLatest commit: b306759 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
This is an update the versioning strategy in #1557: the main benefit was really the pinning react-aria/react-stately because we depend on private APIs and things have broken in minor/patch versions so the idea with this is that we'll keep react-aria/react-stately pinned to exact versions everywhere and we'll never bump react-aria/react-stately in patch versions so using a ~ on the @keystar/ui version is safe and we don't need to do as many releases of @keystatic/core and Keystone which will use the same strategy.