-
Notifications
You must be signed in to change notification settings - Fork 23
Add changelog generation to release process #454
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| echo 'notes<<RELNOTESEOF' >> $GITHUB_OUTPUT | ||
| cat CHANGELOG.next-release.md >> $GITHUB_OUTPUT | ||
| printf '\nThis release is based on the following upstream versions:\n\n' >> $GITHUB_OUTPUT | ||
| ./gradlew -q printUpstreamDependenciesMarkdown >> $GITHUB_OUTPUT | ||
| echo 'RELNOTESEOF' >> $GITHUB_OUTPUT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[minor] could it be simpler to implement this completely as a gradle task ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it would be really simpler because then the gradle task would have to do the file handling, which is more code than cat CHANGELOG.next-release.md.
The multiline support code echo 'notes<<RELNOTESEOF' >> $GITHUB_OUTPUT and echo 'RELNOTESEOF' >> $GITHUB_OUTPUT would still be required, so we wouldn't save much
CHANGELOG.next-release.mdto the repository: This file will contain unreleased changesCHANGELOG.mdto the repository: This file will contain changelogs for all released versionsCHANGELOG.next-release.mdwill be prepend with a new heading for the version toCHANGELOG.mdon release AND used for the GH release notesExample:
I've tested the release note generation steps using GH actions in my fork of the repo.