chore(release): prep 0.0.1 - #33
Merged
Merged
Conversation
First stable — promotes the rc line to 0.0.1 (no prerelease suffix), which the release workflow will publish under the npm `latest` dist-tag. Consumers doing plain `pnpm add @conversed/core` will finally get a current build instead of rc.5. - All four package.json versions bumped in lockstep via scripts/bump-version.sh. - Pinned @conversed/core cross-deps in react/angular updated to 0.0.1. - pnpm-lock.yaml refreshed. Tag `v0.0.1` on main after this merges to fire the release workflow. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Update the Version scheme section to reflect the decision to promote the rc line to a plain 0.0.1 (rather than the previously-suggested 0.1.0). Notes why the promotion works semver-wise and what the next release numbers look like. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Promotes the release-candidate line to the first stable version.
What lands after tag
Once merged, tag and push:
The release workflow publishes all three packages with the latest dist-tag (auto-derived from the plain version). pnpm add @conversed/core will finally resolve to a current build — today it still gets 0.0.1-rc.5.
Note on version choice
docs/releasing.md currently suggests 0.1.0 as the first stable. Going with 0.0.1 because that is what was asked, and it is what the whole rc line has been rehearsing. If you want to switch to 0.1.0 instead, close this PR and I will cut a new one — either works. Docs update to reflect the actual first-stable version can come as a follow-up once we know which one lands.
Test plan