fix: update release-please manifest to current version 1.0.2 #44
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
The manifest was set to 1.0.0 but the actual codebase is at 1.0.2 (per pyproject.toml and CHANGELOG.md). This caused release-please to look at all commits since 1.0.0 and bump to 1.0.1 instead of properly detecting the breaking change (commit 7559751) that should bump to 2.0.0. By setting the manifest to 1.0.2, release-please will only consider commits after that version, properly detecting the breaking change and bumping 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.
Problem
PR #41 is still creating version 1.0.1 instead of 2.0.0. The root cause is a mismatch between:
1.0.01.0.2(per pyproject.toml and CHANGELOG.md)Release-please was looking at ALL commits since 1.0.0, seeing older non-breaking commits, and bumping to 1.0.1 - completely missing the breaking change in commit 7559751.
Solution
Update
.release-please-manifest.jsonfrom1.0.0to1.0.2to match the actual current version.This tells release-please: "The codebase is currently at 1.0.2, only look at commits after that." When it does, it will find the breaking change (commit 7559751: dropping Python 3.7-3.9 support) and properly bump to 2.0.0.
After Merge
Context
Versions 1.0.1 and 1.0.2 exist in CHANGELOG.md but were never properly released through release-please. They only exist as manual version bumps in pyproject.toml without corresponding git tags.
🤖 Generated with Claude Code