slachiewicz commented on PR #333: URL: https://github.com/apache/maven-gh-actions-shared/pull/333#issuecomment-6025507490
The bump is safe for the Maven repositories. The shared config already uses the category model (#315): the latest Release Drafter runs in maven-surefire and maven-resolver print no deprecation warnings on 7.7.0, and none of the 75 `.github/release-drafter.yml` files in apache/maven-* overrides a legacy key. 7.9.0 keeps the `config-name`, `version` and `commitish` inputs this workflow passes, and the 7.8.0 token change does not affect it, since the workflow passes no token. Not yet run here: the job grants only `contents: write`, while the release-drafter README also lists `pull-requests: read`. Findings from moving codehaus-plexus and MojoHaus to 7.9.0 this week, for when we adopt release-drafter/release-drafter#1725 here: - `group-changes` with a Dependabot pattern would have cut 176 of 541 entries across the last 45 plexus releases; plexus-build-api 1.3.0 goes from 44 to 18. Config in use: https://github.com/codehaus-plexus/.github/blob/master/.github/release-drafter.yml - A grouped entry needs `$NUMBERS` in `change-template` to list every PR; `$NUMBER` keeps only the newest. - `$RESOLVED_TAG` gives a compare link that carries the tag prefix: `[Full changelog](https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...$RESOLVED_TAG)`. - 7.7.0 drops an unknown key such as `group-changes` silently, but prints `$NUMBERS` and `$RESOLVED_TAG` literally, so those changes wait until every caller runs 7.9.0. Callers at `@v5` get it from this PR; a repo pinning release-drafter itself does not. - 7.9.0 renders a bot author as a link to the app, so `@$AUTHOR` shows `@` followed by a linked `dependabot[bot]`. All MojoHaus repos that draft releases now call this workflow at `@v5`, so this bump also unblocks mojohaus/.github#9. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
