Skip to content
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

Automate release with JReleaser #3600

Merged
merged 2 commits into from
May 11, 2024
Merged

Automate release with JReleaser #3600

merged 2 commits into from
May 11, 2024

Conversation

filiphr
Copy link
Member

@filiphr filiphr commented May 9, 2024

Add JReleaser for automating the release and add a step for automating the publishing of the website

This has been heavily inspired by the Moditect and JReleaser release procedures.

Not sure if @aalmiray, the creator of JReleaser, might be able to chime in and let us know if I'm doing something incorrectly here. Not sure what the best approach would be to test this with an actual Maven release.

I think doing the 1.6.0.Beta2 release would be a good first try for this.

Closes #3602

Add JReleaser for automating the release and add a step for automating the publishing of the website
@aalmiray
Copy link

aalmiray commented May 9, 2024

FWIW you can test most of the release configuration locally. You may run mvn jreleaser:jreleaserConfig to print out the resolved configuration. You may also run a release in dry run mode.

More tips can be found at https://jreleaser.org/guide/latest/checklist.html

parent/pom.xml Outdated Show resolved Hide resolved
parent/pom.xml Outdated Show resolved Hide resolved
parent/pom.xml Show resolved Hide resolved
@filiphr
Copy link
Member Author

filiphr commented May 10, 2024

Thanks a lot for the comments @aalmiray. I was already trying it with the dry run locally and it looked like it is working correctly.

Thanks a lot for your work on JReleaser, I think automating the release is going to make us release faster 😄

@filiphr filiphr merged commit 9a5e6b1 into mapstruct:main May 11, 2024
6 checks passed
@filiphr filiphr deleted the jreleaser branch May 11, 2024 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automate releases using JReleaser
2 participants