Closed Vampire closed 6 years ago
And to be more specific, it is the last .update()
call that breaks it.
While switching the draft state should not break the release, actually the whole call is unnecessary here, as the release is already in draft state actually.
I'd say this is a bug in GitHub actually, if I use HTTPie it is the same.
If I patch the release to draft=true
it sometimes changes the tag name to untagged-<whatever>
.
Would you mind releasing a version with release.update().draft(isDraft()).update()
replaced by release.update().draft(isDraft()).tag(getTagName()).update()
soon, or even better if (release.draft != isDraft()) { release.update().draft(isDraft()).tag(getTagName()).update() }
, as an unnecessary call is prevented then.
I made PR #19 that fixes this and while I was at it also #17.
Would be nice if you could release that soon, as I cannot finish the PR I'm preparing with your plugin if this doesn't work properly.
The line
release.update().draft(isDraft()).update()
corrupts the release tag. Before the line (breakpoint on the line): After the line (stepped over) Which will result in a new tag calleduntagged-4b7ab7ff233227717a2d
on the currentmaster
commit instead of on the tag when the release is published without fixing it first.