cc/ @softprops for review 🙇

I'm curious, would this also upload to an existing draft release (and keep it a draft) even if the draft key is not present?

I'm curious, would this also upload to an existing draft release (and keep it a draft) even if the draft key is not present?

This is a great question! You can't update a draft release without the draft key. And looks like it's not possible to publish a draft release with this action. I think it good to have this ability

@itoys can you fix the merge conflicts? Thanks!

Closing this out in favor of the docs clarification merged in #759.

Current master already supports the draft-reuse behavior this PR was targeting:

• keep the reused release as a draft when draft: true is set
• reuse the same draft release and publish it after upload when draft is omitted

Fresh verification:

• keep mode: https://github.com/ruitest2/action-gh-release-test/actions/runs/23104088782
• publish mode: https://github.com/ruitest2/action-gh-release-test/actions/runs/23104088778

If you still see a different draft-update gap on a current release, please open a fresh issue with a minimal repro.