getDefaultComponent doesn't find the right packageName if includeComponentInTag is set to false and it is for a nested path #2214
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
I was investigating why release-please did not open a PR here: googleapis/gax-nodejs#1553
The CLI does not tag the PR with the warning:
⚠ PR component: undefined does not match configured component: google-gax
(here):
release-please/src/strategies/base.ts
Line 615 in 72b0ab3
PR component: ${branchName.component} does not match configured component: ${branchComponent}
That is true, since the branch does not contain the component:
There's a bug that occurs when setting the branchName in
buildPullRequests
in manifest, it will return empty hereI think that's because
getBranchComponent
returns an empty string here:release-please/src/strategies/base.ts
Line 176 in 72b0ab3
A workaround I'll try in the meantime is just to specify it in the config object explicitly - that should work. But I think the better functionality is to automatically grab it from the nearest package.json
The text was updated successfully, but these errors were encountered: