chore: add changeset for 0.8.0 correctness fixes#80
Merged
Conversation
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.
Back-fills a Changesets entry for the ~28 user-facing bug fixes that landed since v0.7.0 but had no changeset. Without this, the 0.8.0 package CHANGELOGs would only document the share-groups GA work (#77) and ship all these fixes undocumented on npm.
patch(per the repo's Versioning convention). The existingshare-groups-v2minorchangeset keeps the release at 0.8.0.Once merged, the Release workflow will regenerate the open #78 "chore: version packages" PR with the complete 0.8.0 CHANGELOG. Merging #78 then publishes 0.8.0 to npm, tags
v0.8.0, and creates the GitHub release.Verified locally with a throwaway
changeset version— renders cleanly and resolves to 0.8.0.