smallrye-mutiny: Fix JReleaser not working anymore
With the update to the SmallRye release workflows, JReleaser is not working anymore:
- GitHub release notes are not computed properly
- GitHub discussions announcements are not working anymore.
In the interim I have added a task in justfile (aka just jreleaser) that replicates what was previously working in CI.
When we do this locally a proper changelog is being computed, but the GitHub release note isn’t updated so we need to do that manually. Still, the Maven plugin is configured with overwrite to yes, so this should perform the update according to the JReleaser docs.
The major change compared to the previous workflow (see at tag 2.6.2 https://github.com/smallrye/smallrye-mutiny/tree/b6b0934ee5594630347079426d2a1721d08ab3d9) is that JReleaser is not doing the release and tagging anymore as this is now done by the maven-release-plugin in the prepare-release.yml workflow. The JReleaser configuration has been updated to reflect that change properly (<skipTag>true</skipTag>).
One thing we might explore (first week of November) is to replace the prepare-release.yml workflow by using JReleaser again to tag and release with it, which would have us adopt half of the classic SmallRye release workflows.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 32 (17 by maintainers)
Might be related to a push I made yesterday evening when computing the target commit to be tagged. The change was reverted a few hours ago. Latest early-access release should have the fix.
Ah. That confirms it. I have a bug to file and fix.
I ran a local release and diffed the logs from what you posted. I get pretty much the same results except for the repo owner which was set to
aalmiray. At the moment I cannot find the reason for the errors you’re seeing.Skipping merge commits still make the changelog too big
However JReleaser will truncate the release notes while uploading them as a separate release asset