chore: cut the 1.0.0 stable release#23
Merged
Merged
Conversation
Marks the public API as stable (semver from here on) and forces release-please to cut 1.0.0 via release-as. The API was reviewed and frozen across the 0.3.x/0.4.0 work; coverage and error paths are hardened.
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.
Promotes the SDK to 1.0.0 — the public API is reviewed, frozen, and follows semver from here.
Changes
"release-as": "1.0.0"— forces release-please to cut 1.0.0 instead of the next 0.x minor. (Using the config field, not aRelease-As:commit footer, because squash merges use the PR title only and drop the body.)Why now
Across 0.3.0 → 0.4.0 we landed full endpoint coverage, reviewed and froze the public API surface (return conventions, param typing, naming), fixed the release tooling, and hardened error/edge-path coverage (branches 85% → 92.5%, lines 99.2%). Nothing material is pending.
Flow after merge
release-asso later releases auto-increment from 1.0.0. (It is sticky — must be removed, or every run re-cuts 1.0.0.)🤖 Generated with Claude Code