docs(changeset): describe 0.1.0 as a release, not a migration - #54
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Merges the two pending changesets into one initial-release description, so the published 0.1.0 changelog reads as a release note rather than a migration guide.
Why
rsc-namespace-exports.mdopened with:That was accurate as a description of PR #53's effect on
main, but 0.1.0 is the first published version — there is no<Composer>for anyone to migrate from. As the top item on the npm page it would tell a first-time reader that something broke in a version they never had.What changed
initial-release.mdnow describes the shipped surface directly: namespaces with explicit.Rootparts, and React Server Component support as a capability rather than as a fix. Thersc-namespace-exports.mdchangeset is removed, since its content is folded in.No code change, and the bump is unaffected — still a single
minor, 0.0.0 → 0.1.0.Verified
Ran
changeset versionagainst a throwaway clone: version resolves to 0.1.0 and the generatedCHANGELOG.mdcontains one coherent entry with no "Breaking" heading.changeset statusstill reports@intentface/chatatminor.Note on merging
This regenerates #52. After merging, wait for the Release workflow to update the Version Packages PR, then confirm its
CHANGELOG.mddiff shows the single entry before merging that.