release-please: Release please no longer making release PRs (There are untagged, merged release PRs outstanding - aborting)
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
- OS: google-github-actions/release-please-action@v3
- Node.js version: google-github-actions/release-please-action@v3
- npm version: google-github-actions/release-please-action@v3
release-pleaseversion: google-github-actions/release-please-action@v3
Information
Somehow my repository ( https://github.com/case-contract-testing/contract-case ) has got into a state where release PRs are no longer being created due to:
⚠ There are untagged, merged release PRs outstanding - aborting
I tried to fix this by manually tagging a past release PR (which worked for generating this release PR), but after merging it, no tags or releases were generated, and the repo was left in this state again.
Steps to reproduce
- Unclear, I’m afraid
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 8
- Comments: 34 (17 by maintainers)
Commits related to this issue
- ci: convert release to semantic-release release-please error'd too often with "There are untagged, merged release PRs outstanding - aborting" and I couldn't get it to comply. Also see https://github.... — committed to sne11ius/pp by sne11ius 2 years ago
- ci: convert release to semantic-release release-please error'd too often with "There are untagged, merged release PRs outstanding - aborting" and I couldn't get it to comply. Also see https://github.... — committed to sne11ius/pp by sne11ius 2 years ago
Thanks. That’s how I manually fix this every time I merge a release pr:
autorelease: pendinglabel from all PRsThis will get it to generate the release PR again.
However, when you merge that release PR, release-please still doesn’t create any releases.
For example, this recently merged PR, resulted in this github actions run, which aborts with:
(which is the exact release PR it is supposed to be processing).
@chingor13 the original problem is not fixed
@SurferJeffAtGoogle Could you give some insight on why this was deprioritised? I’m kind of frustrated that deprioritising it is the only interaction we’ve had from a maintainer 😕
I found this issue today. Have removed all the pending tags, even for the closed ones, also tried to push new commits, the PR gets generated, but after I merge it, it does not generate the tag/release and can’t trigger the next process that is build and publish the image (because this is the first step of my release).
@chingor13 Unless you’re about to merge something that fixes this, I don’t think this is fixed.
@TimothyJones Github PRs created by
release-please-actionsare tagged with labels named likeautorelease:*. I tried to remove these labels from all PRs (include closed PRs), then re-run workflows and suceed !I took a look at your repo: Remove
autorelease: pendingfrom the merged revert release PR.Yes, that sounds like the bug I’m reporting here
Tbh, I can’t really recommend this library without a fix for this bug. The “workaround” is to manually tag the versions, and so release please is only used for generating changelogs.
@sebastianfelipe I also just started hitting this within the past hour or two. Github seems to have labels changing at a very slow rate and causing something to go wrong in the GH action flow. This also corresponds with a number of reports of errors to downdetector. Hoping it will resolve
Same issue
So, this is still happening.
I had thought that it might be because I’d corrupted the tags somehow. I tried cloning the repository without any tags and doing a bootstrap, but it still won’t make releases after the release PR is merged.
The logs from a merge of a PR that should have made a release can be seen here
Any ideas?