github-release command quit when get 'Bad pull request title'

[leavesster]

Environment details

• OS: Ubuntu
• Node.js version: 20
• npm version: 10
• release-please version: 16.12.0

Steps to reproduce

Set "group-pull-request-title-pattern" value as "chore${scope}: releases packages ${component} ${version}" like this in monorepo .
when in monorepo the merge plugin will make ${component} ${version} be undefined. so the title output will be "chore(main): releases packages"

You can get the message reproduce from my action log and commit

release-please/src/util/pull-request-title.ts

Line 24 in ace2bd5

export function generateMatchPattern(

this function will generate Regex the pattern as /^chore(\((?<branch>[\w-./]+)\))?: releases packages ?(?<component>@?[\w-./]*)? v?(?<version>[0-9].*)$ which won't match the default value: "chore(main): releases packages".

This make github-release command early return and won't create release and tags. the detail code is in

release-please/src/strategies/base.ts

Line 591 in ace2bd5

this.logger.error(`Bad pull request title: '${mergedPullRequest.title}'`);

so this will be unable to release a tag.

---

After a few hours search. My believe the pullRequestTitle can be undefined. because the release just need get version from the title in

release-please/src/strategies/base.ts

Line 651 in ace2bd5

let version: Version | undefined = pullRequestTitle.getVersion();

But it can also get from pullRequestBody. so we can just throw the pullRequestTitle away.
I've already test locally and glad to give a pull request if you want.

[realmunk]

Ran into this issue when using the GitHub app for Release Please. This was really tough to debug, and made me question if this was a branch protection issue or similar. Did not find any error logs.

In addition to fixing this issue – would it make sense to perhaps add a label or similar that can trigger debug logs for the GitHub app?