chore: release main#78
Closed
StefanSteiner wants to merge 2 commits into
Closed
Conversation
5 tasks
StefanSteiner
added a commit
that referenced
this pull request
May 29, 2026
Configures release-please to bump 0.x.y → 0.(x+1).0 on a BREAKING CHANGE: footer instead of bumping straight to 1.0.0. The default release-please behavior for any 0.x.y release-type:simple package is that BREAKING CHANGE triggers a 1.0.0 bump; bump-minor-pre-major:true overrides that to "BREAKING CHANGE while < 1.0.0 only bumps minor". Why now: PR #77 (the v0.3.0 rollup) carries a BREAKING CHANGE: footer. release-please opened release PR #78 proposing 1.0.0. We closed #78 without merging — the manifest is still 0.2.3, no tag was cut. With this config change, the next release-please run will recompute against main and propose 0.3.0 instead of 1.0.0. Schema verification: bump-minor-pre-major is a documented field on the release-please config schema at both the top level (acts as default for all packages) and the per-package level. Verified against https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json and the implementation in release-please src/manifest.ts:1746-1747 which reads pathConfig.bumpMinorPreMajor ?? defaultConfig.bumpMinorPreMajor. Setting both explicitly for defense-in-depth. This config is evaluated against current commits at run time, so it applies retroactively to the BREAKING CHANGE: footer already on main. No need to amend the rollup commit or cherry-pick history. Note: the closed PR #78 still has the autorelease: pending label. That label only matters on OPEN PRs; release-please's matcher (findOpenReleasePullRequests) ignores closed ones unless they carry autorelease: snooze. PR #78 is therefore invisible to the next run, which will open a fresh release PR with the corrected 0.3.0 proposal.
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.
🤖 I have created a release beep boop
1.0.0
1.0.0 (2026-05-28)
⚠ BREAKING CHANGES
Features
This PR was generated with Release Please. See documentation.