fix: add release-please v4 configuration files #42
Conversation
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
Add required configuration for release-please v4: - .release-please-manifest.json: Tracks current version (1.0.0) - release-please-config.json: Configures release strategy for Python package Without these files, release-please v4 cannot properly detect and bump versions for breaking changes. This will allow the breaking change in commit 7559751 to properly trigger a major version bump to 2.0.0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Adds the required configuration files for release-please v4 to properly detect and handle breaking changes.
Problem
PR #41 is creating release 1.0.1 instead of 2.0.0, even though commit 7559751 contains a breaking change. This is because release-please v4 requires configuration files that were missing.
Changes
New files:
.release-please-manifest.json: Tracks the current version (1.0.0 from last git tag)release-please-config.json: Configures the Python release strategyAfter Merge
Once this PR is merged:
References
🤖 Generated with Claude Code