GitHub releases provider: force_update option always makes the target release a draft

yncat's Avatar


26 Sep, 2020 09:20 AM


Under the following appveyor.yml setting, the target release is forcefully changed to draft even if draft: false is defined.

  - provider: GitHub
    release: snapshot
    skip_tags: true
    Force update: true
    description: 'automatic build from master branch'
      secure: xxxxxxxx
    draft: false
    prerelease: false
      branch: master # release from master branch only

I want to replace the existing artifact, but don't want the draft status to be changed.

(1) Is this an expected behavior in Appveyor?
(2) Any solutions?

What I want to do is making snapshot build which is synced to the latest default branch.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac