tag:help.appveyor.com,2012-11-13:/discussions/problems/28271-github-releases-provider-force_update-option-always-makes-the-target-release-a-draftAppVeyor: Discussion 2020-09-26T09:24:43Ztag:help.appveyor.com,2012-11-13:Comment/486663672020-09-26T09:20:49Z2020-09-26T09:24:43ZGitHub releases provider: force_update option always makes the target release a draft<div><p>Hello.</p>
<p>Under the following appveyor.yml setting, the target release is forcefully changed to draft even if draft: false is defined.</p>
<p>deploy:<br>
- provider: GitHub release: snapshot skip_tags: true Force update: true description: 'automatic build from master branch' auth_token: secure: xxxxxxxx artifact: snapshot.zip draft: false prerelease: false on: branch: master # release from master branch only</p>
<p>I want to replace the existing artifact, but don't want the draft status to be changed.</p>
<p>(1) Is this an expected behavior in Appveyor? (2) Any solutions?</p>
<p>What I want to do is making snapshot build which is synced to the latest default branch.</p></div>yncat