chore: release 0.12.0 (Release-As override — minor, not major) - #376
Merged
Conversation
Force release-please to cut a minor release (0.12.0) instead of the major (1.0.0) it currently proposes in the release PR. The single breaking change (omezarr z5 3.0.1 / C++20 migration) triggered a 0.x->1.0.0 major bump even though release-please-config.json sets bump-minor-pre-major:true — that config isn't being honored (the workflow drives release-please-action@v4 with inline release-type/package-name instead of config-file/manifest-file). This override pins the next release to 0.12.0. Release-As: 0.12.0 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sameeul
added a commit
that referenced
this pull request
Jul 17, 2026
…pin 0.12.0 The release PR (#344) proposed 1.0.0 because the workflow drove release-please-action@v4 with inline release-type/package-name, which put v4 on the non-manifest path and ignored release-please-config.json — where bump-minor-pre-major:true already asks for 0.x breaking changes to bump the minor (0.11.0 -> 0.12.0), not jump to 1.0.0. Switch to config-file/manifest-file so the policy is honored. Also pin this release explicitly via the footer below in case the config wiring needs a cycle to take effect. (The prior empty-commit Release-As in #376 was dropped by rebase-merge and never reached main; this carries the footer on a real change so it survives any merge.) Release-As: 0.12.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.
Forces release-please to cut 0.12.0 (minor) instead of the 1.0.0 (major) it currently proposes in PR #344.
Why
The only breaking change this cycle is the omezarr z5 3.0.1 / C++20 migration, which drove a
0.x → 1.0.0major bump — even thoughrelease-please-config.jsonsetsbump-minor-pre-major: true(which should keep 0.x breaking changes as minor bumps). That config is not being honored:.github/workflows/release-please.ymldrivesrelease-please-action@v4with inlinerelease-type/package-nameinstead ofconfig-file/manifest-file, so the pre-major policy is skipped and default semver (breaking → major) applies.What this does
An empty commit carrying the
Release-As: 0.12.0footer. On merge tomain, release-please rewrites PR #344 to0.12.0(version, CHANGELOG,.release-please-manifest.json,setup.py,.versionall consistent) instead of 1.0.0.Release-As: 0.12.0
Recommended follow-up (separate)
Fix the workflow to pass
config-file: release-please-config.json+manifest-file: .release-please-manifest.json(and drop the inlinerelease-type/package-name) sobump-minor-pre-majoris honored and future 0.x breaking changes don't need a manual override.🤖 Generated with Claude Code