chore: release 1.0.0#24
Merged
Merged
Conversation
The config release-as field set the version but did not trigger a release (release-please needs a user-facing commit). The 1.0.0 cut is instead driven by a Release-As footer on this commit, which forces the release and is one-shot.
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.
Triggers the 1.0.0 release.
The previous attempt set
release-asin the config, but that only sets the version number — it does not trigger a release (release-please skips when there are no user-facing commits since the last tag, and we only havetest:/chore:since 0.4.0). This PR removes that ineffective (and sticky) config field; the release is instead forced by aRelease-As:footer on the merge commit, which both triggers the release and is one-shot (no cleanup needed).When you click Squash and merge, add this line to the commit message body (the box under the title) before confirming:
That footer forces release-please to open a release 1.0.0 PR. Merge that → 1.0.0 publishes to npm. No further cleanup.
(If the footer is missing, nothing breaks — release-please just won't cut a release, and we retry.)
🤖 Generated with Claude Code