Published release became draft after update

Describe the bug

Published release became draft after update.

To Reproduce

1. Create draft release with release-action
2. Publish it manually
3. Update release with option allowUpdates: true
4. Published release became draft

Expected behavior

It would be great to have option such changeDraftDuringUpdate to be able to keep release published during update.

- uses: ncipollo/release-action@v1
  with:
    tag: v${{ env.VERSION }}
    name: v${{ env.VERSION }}
    draft: true
    changeDraftDuringUpdate: false
    allowUpdates: true
    omitBodyDuringUpdate: true
    omitNameDuringUpdate: true

[ncipollo]

Got it, thanks for providing more context. I’ll add an option to avoid applying the draft flag if the release exists.

[ilg-ul]

you can fork the action and change the default.

No problem, once you add this option I can update the repos, I use a template and I can easily re-generate the configurations.

Just make sure that the documentation warns the users on the danger of re-enabling the draft option.