Hello everyone, For what’s worth JReleaser supports a similar set of features for creating a changelog based on Git history.
For the time being JReleaser categorizes commit messages following your own conventions. The rules are inspired by release-drafter. The pros are: - set up your own conventions - generated changelog can be stored anywhere, not just at the GH mirror - may be used via jreleaser-maven-plugin - works locally and on CI - can post releases as drafts to allow manual edits - can use templates to tweak parts or the whole changelog - initial tag/release is configurable. Matter of fact may be uses to retroactively generate Git releases + changelog on projects that only have tags - works with any Git service as it only requires reading local commit information The cons are: - does not read issue/PR labels to categorize commits. This feature may be added in the future - some features require a local GH token for read access (when resolving username/emails from GH) A PR is currently underway at the mvnd project to test it out https://github.com/apache/maven-mvnd/pull/574 Disclaimer: I’m the author of JReleaser. Cheers Andres Sent from my primitive tricorder > On 9 Feb 2022, at 17:04, Tamás Cservenák <[email protected]> wrote: > > Howdy, > > Yes, looks good, but one thing bothers me: > Does this mean that Maven projects -- if release-drafter is to be used -- > will have their release notes stored and accessible in their mirror > repositories only? > > T > >> On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski <[email protected]> >> wrote: >> >> Looks great. >> >> To avoid all PR in the first release we can add an empty release note for >> the latest release tag and then the new release draft should contains only >> PR from the latest release not all. >> >> śr., 9 lut 2022 o 05:10 Olivier Lamy <[email protected]> napisał(a): >> >>> Hi >>> Github has a feature to attach a release note to tag/release. >>> The content is then used when dependabot generates his famous PR all >>> over the world!! (yup a maven plugin generates a lot!!) >>> Our current content is not very user friendly.... >>> >>> While preparing the maven-compiler-plugin new release I have made some >>> tests using release-drafter tool [1]. >>> This generates the content here: >>> https://github.com/apache/maven-compiler-plugin/releases >>> The release notes will automatically contains only content from PRs (PR >>> must have a label to appear in a dedicated section otherwise they will be >>> in the top, see mapping label/section here [2]) >>> This mapping is a default which can be shared between all project so the >>> configuration is very simple see [3]. >>> Please note the first time it's used the first release will >>> contain everything (all PRs) from the start as there is no first release. >>> The process is manual at the end, after all of our release process steps, >>> you just need to go to GH ui then publish the release (manual. >>> modifications still possible). >>> >>> comments? thoughts? complaints :)? >>> >>> cheers >>> Olivier >>> >>> PS: if you want to use this be sure to modify manually the content before >>> the publish as the content is regenerated for every merge PR >>> >>> [1] https://github.com/release-drafter/release-drafter >>> [2] >>> >>> >> https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml >>> [3] >>> >>> >> https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml >>> and >>> >>> >> https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml >>> >> >> >> -- >> Sławomir Jaranowski >>
