Skip to content

There are untagged, merged release PRs outstanding - aborting on other branch than default #1444

@paoll

Description

@paoll

When using release-please-action on another branch than the default one, the PR is correctly opened, but once merged it fails to create the release:

 ✔ Looking for latest release on branch: hotfix/v3.1.0-bug with prefix: <repository-name>
✔ Building releases
✔ Building strategies by path
✔ Building release for path: .
⚠ pullRequestTitlePattern miss the part of '${scope}'
⚠ pullRequestTitlePattern miss the part of '${component}'
⚠ pullRequestTitlePattern miss the part of '${version}'
✖ Bad pull request title: '[HOTFIX] - chore(hotfix/v3.1.0-bug): release 3.1.0-hotfix1'
✔ No release necessary for path: .

✔ Looking for latest release on branch: hotfix/v3.1.0-bug with prefix: <repository-name>
✔ Building pull requests
✔ Building strategies by path
✔ Collecting release commit SHAs
✔ Collecting commits since all latest releases
✔ Splitting 4 commits by path
✔ Building candidate release pull request for path: .
✔ Considering: 5 commits
⚠ There are untagged, merged release PRs outstanding - aborting

The PR is still labelled as autorelease: pending, thus the release is not created.

My configuration is the following one:

[...]
      - uses: google-github-actions/release-please-action@v3
        with:
          release-type: simple
          package-name: ${{ github.event.repository.name }}
          token: ${{ secrets.token }}
          default-branch: ${{ github.ref_name }}
          pull-request-title-pattern: "[HOTFIX] - chore${scope}: release${component} ${version}"
          monorepo-tags: false

There is a related issue on https://github.com/google-github-actions/release-please-action/issues/443

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions