dpl: Problems with GitHub deploy updating Release body

There seems to be an issue with updating the Release body message.

We have the following case:

Our build under https://travis-ci.com/github/virtualsatellite/VirtualSatellite4-DEV-IDE/builds/175412233 is running an integration build. It is setting the integration_snapshot tag always to the latest commit on the integration branch. Once the build is succesful some files are uplaoded to the integration Release https://github.com/virtualsatellite/VirtualSatellite4-DEV-IDE/releases . The body of the release message should be updated with the time and commit sha of the build.

This used to work fine and stopped meanwhile. Today it seems the release message is not getting changed at all when deploying.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 2
  • Comments: 15 (7 by maintainers)

Most upvoted comments

@Velenir Happy to hear that it works for you now. I apologize for the confusion about the v2; I’ll work on improving the docs.

I didn’t know specifics about v2 😞 . edge worked great

Than you very much! 🎉

v1.3.0-test.20 uses release_note which should be the same as body as far as I understand

dpl v1 does not understand release_notes.

Disabling build config validation doesn’t help

Have the same issue Body stopped being filled somewhere between Jan 7 and Jan 27

Tried out using release_notes instead of body, to no avail. On the other hand, file gets posted to releases without problem

Additional Info. Judging from our build history, It seems that the feature was working at least until 14. January 2020