chore: force next release to 1.1.0 via release-as config #187
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
Closed
jhcipar
approved these changes
Feb 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Add
release-as: "1.1.0"configuration to force release-please to create version 1.1.0 instead of 2.0.0.Why This Change
Release-please automatically bumped to 2.0.0 due to breaking change markers in conventional commits. We want to release 1.1.0 instead.
How It Works
The
release-asconfiguration option overrides automatic version calculation and forces release-please to use the specified version (1.1.0).Post-Merge Actions Required
CRITICAL: After this PR is merged and the 1.1.0 release PR is created and merged, we MUST remove the
release-asconfiguration. Otherwise, release-please will continue trying to create 1.1.0 releases even after it's been released.References
Test Plan
release-asconfiguration immediately after