ci: the release pull request says which release it is - #47
Merged
Merged
Conversation
ExtraToast
changed the title
Every release pull request here is titled `chore: release main`, because
`separate-pull-requests: false` turns on the merge plugin — which a
single-package manifest does not need, and which reads
`group-pull-request-title-pattern`, not the `pull-request-title-pattern` this
file sets. That default is `chore: release ${branch}`, so the configured
request for the version was never consulted.
Both keys go. The built-in default, `chore${scope}: release${component}
${version}`, is what the rest of the estate shows: `chore(main): release
0.6.0`.
The head branch does not move — five workflow conditions name it — because a
single-package release with no `package-name` keeps
`BranchName.ofTargetBranch`.
ExtraToast
force-pushed
the
chore/release-please-title
branch
from
September 16, 2026 18:17
30daa86 to
3c3c71e
Compare
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.
Refs ESA-Blueshell/website#1243.
Why
Every release pull request here is titled
chore: release main. The version it would publish is not in the title, so one release pull request reads exactly like the last one — in a list, in a notification, and in the merge commit it becomes.What this achieves
chore(main): release X.Y.Z, which is whatJorisJonkers-dev/deploy-kit,nix-configandapi-contract-checksalready say.How
Two keys go.
separate-pull-requests: falsewas the cause. In release-please'smanifest.tsthe default isObject.keys(repositoryConfig).length === 1— already true for a single-package manifest like this one. Setting it tofalseturns the merge plugin on regardless, and the merge plugin readsgroup-pull-request-title-pattern, notpull-request-title-pattern. Its default ischore: release ${branch}, which is wheremaincomes from.pull-request-title-pattern: "chore: release ${version}"goes with it: unread while the merge plugin was on, and unnecessary once it is off, because the built-in default ischore${scope}: release${component} ${version}— the same thing plus the branch scope the rest of the estate shows.Not in scope
The branch name.
release-please--branches--mainis named inrelease.ymlhere and in five workflow conditions in the two client repositories, so it must not move — and it does not: withpackage-nameunset, a single-package release keepsBranchName.ofTargetBranch.nix-configandapi-contract-checksare the evidence, with the right title on that same branch.Verification
The configuration parses as JSON and keeps its schema reference. The next release pull request is where the title is visible; the open one carries the
autorelease: pendinglabel, so release-please updates it in place rather than opening a second.