chore: release as 1.0.0#12
Merged
Merged
Conversation
Revert the premature manual version bump so pyproject.toml matches the release-please manifest (0.2.0) between releases. The Release-As footer forces the next release PR to 1.0.0 instead of the computed 0.3.0. Release-As: 1.0.0 Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Force the next release to
1.0.0via aRelease-Asfooter instead of the conventional-commit computed0.3.0.What this does
pyproject.tomlbump (1.0.0→0.2.0) so the working version matches.github/.release-please-manifest.jsonbetween releases. release-please will set it to1.0.0in the regenerated release PR.Release-As: 1.0.0in the commit body. The footer must survive the squash merge — keep it in the squash-commit message, otherwise release-please won't see it onmain.After merge
release-please re-opens the release PR (currently #11
release 0.3.0) asrelease 1.0.0. Merging that release PR tagsv1.0.0and triggers the PyPI publish job.🤖 Generated with Claude Code