You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
{
".": "1.0.3"
}
Here's what the release-please-config.json looks like:
megancoyle
changed the title
After merging a release PR, a release is created but then another release PR is automatically opened
After merging a release PR, a release is created but then a duplicate release PR is automatically opened
Mar 21, 2024
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.
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
The text was updated successfully, but these errors were encountered: