on 08 Jan, 2018 09:43 PM
I think I'm having a similar problem.
For facebook/flow, we push a tag, then use the GitHub API or web UI to create the release, writing a custom release description. Meanwhile, appveyor creates the windows build and uploads it to the existing release, but it also either overwrites the description with the commit message, or erases the existing description causing github to fall back to the commit message, because the `description` field in the `deploy` config isn't set. Not sure which is happening but the result is that the custom description is replaced by the commit message.
We have `force_update` set to true, because at the time it was failing to upload the artifact to an existing release without it, but based on the OP it sounds like maybe that's no longer an issue. Trevor, are you using force_update?
Please watch this issue. Fix will be deployed in a week or so.
However, as Marshall noted, if you need only artifact upload you can simple remove force_update: true (or uncheck Update release details if exists is you use UI). If you still need other release details to be updated, please watch issue mentioned above.
Hi - Sorry for my delay to respond. Yes, I am using force_update: true.
I solved my specific issue by constructing an environment variable that is the same as the annotation and placing it at release: $(RELEASE_LABEL) under deploy.provider...
However, it looks like the problem is the same as Marshall's and I would have the same behaviour if my annotation was dynamic. Cheers.