Open megancoyle opened 5 months ago
I have the same problem.
this is also giving us issues
having the same issue and I think I found the root cause. This happens when you have the draft:true
flag set. This is because no git tag is created until the github release is manually published, so release please fails to find the new tag and creates a new PR with exactly the same changes.
I think release please action (or release please) should tag the repo regardless of the value of thedraft
flag.
Tried a workaround using skip-github-release
option and then generating a release in a followup step, but the same problem occurs. No tag is generated and things break
I'm also having this problem. Another issue is that with draft: true
in my release-please-config.json
, release please is grabbing every change since I added in release-please, causing incorrect changelogs and incorrect version bumps.
TL;DR
When using the release-please action, on triggering a release PR, if I merge in the release PR, a release will get created in the draft format, but a duplicate release PR will get opened
Here's an example of what the
.release-please-manifest.json
looks like:Here's what the
release-please-config.json
looks like:Expected behavior
After merging in a release PR, I was expecting a draft release to get created, and no other PR get automatically opened.
Observed behavior
Instead, a duplicate release PR of the one just merged, was getting opened.
Action YAML
Log output
No response
Additional information
No response