Repository navigation
Prepare release 2.11.0 & fix changeset - #869
Merged
Merged
Conversation
ryanmorris708
force-pushed
the
ryan/release-2.11.0
branch
from
November 18, 2026 17:53
3a73d6b to
d48caea
Compare
bossinc
reviewed
Nov 18, 2026
bossinc
approved these changes
Nov 18, 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.
Type of Change
Chore
Prepare to release version 2.11.0. Additionally, add
privatePackagesto the changeset config, which is required by@changesets/cliv3 (recently upgraded) to run changeset commands for a private package (refer to the v3 migration guide). Lastly, remove changesets that have already been released and add them to the changelog under the version they were released with. Note that one patch release, 2.9.4, shipped a feature with it.