Home → Problems →

github force_update set to false still overwrites

• Edit

rodem

14 Jun, 2023 07:18 AM

I may be reading this wrong in regards to force_update: "default is false which will fail deployment if the release already exists on GitHub."

with this section in yaml file:

deploy:
  release: 'v1.3.1' # :bump
  skip_tags: true
  provider: GitHub
  auth_token:
    secure: ......
  draft: false
  prerelease: false

I get this at the end of the build log:
Creating "v1.3.1" release for repository "...." tag "v1.3.1" ...Skipped - release with tag "v1.3.1" already exists
Deleting existing release asset "...setup.exe"...OK
Uploading "...setup.exe" to release assets...OK

I was expecting it to not delete and replace the existing. I have also tried adding force_update: false but no difference.

1. Support Staff 1 Posted by Feodor Fitsner on 14 Jun, 2023 05:35 PM

   

   Right, looks like the docs are incorrect. force_update enables update of Release details if it exists. Release artifacts are always uploaded.

   If you need to fail when release exists you can use a simple script in before_deploy requesting release details using GitHub API.

   • Edit

2. 2 Posted by rodem on 15 Jun, 2023 01:02 AM

   

   Thanks Feodor, nice to know, I can see several ways to work around it so not a big concern but can I ask what exactly force_update: true is for then? The only difference I've noticed is that the '5 commits to since this release` on the release page is missing when not set.

   • Edit

3. 3 Posted by rodem on 15 Jun, 2023 01:07 AM

   

   Sorry, scratch that, I just re-read your reply and it seems that exactly what its meant to do...

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 17 Jun, 2023 06:55 PM

   

   OK, thanks for the update!

   • Edit

5. Feodor Fitsner closed this discussion on 17 Aug, 2023 09:03 PM.