deploy to github releases does not allow us to specify changelog (release notes)

[ssbarnea]

Even if GitHub releases do support release notes (changelog) it seems that using Travis we cannot specify them.

The documentation page from https://docs.travis-ci.com/user/deployment/releases does not any word regarding release notes.

[pjvds]

The github releases API has support for setting the release notes (changelog) via the body field, see: github releases api docs. It would be nice if we get an extra field in the deploy section of the travis.yml to set this value.

[joepvd]

Cross linking to the dpl repository: travis-ci/dpl#155

[ssbarnea]

Any update on this? More than 6 months later and no update regarding uploading the release notes to github. I have lots of users complaining about the lack of release notes / changelog.

@pjvds Please note that I already have the changelog on disk, the only thing we need is to tell travis to load the content of this file as the body parameter.

[thom4parisot]

Hi there,

indeed it would be a lovely addition. The :body field content can be automatically generated via an audit of git logs. It does not necessarily means files are releases too (in the case of tagged npm release for example, the artefact is then hosted on npmjs.com)

[llorllale]

+1

My workaround is attaching a file with the release notes, although having them displayed directly in the release' description is preferrable.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[GhostofGoes]

Any updates on this?

[berry120]

This would be really useful for us as well - we have a CI build that's automatically published as a Github release, and we'd like to be able to add release notes warning that it's an unstable build (it's right there in the title, but people often download it anyway...)

[thom4parisot]

As far as I understand, the underlying library accepts the body argument (cf. Advanced Options). You can populate it with the content of a file (or the topmost section of a CHANGELOG file).

A problem down the line seems to prevent formatted body content.
Someone posted this Gist to workaround this (found in travis-ci/dpl#155): https://gist.github.com/valeriomazzeo/5491aee76f758f7352e2e6611ce87ec1

Looks like it does what we are looking for.