JReleaser v1.26.0 has just been released! The full list of issues can be found at the v1.26.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Packagers Support additional settings in Snapscraft such as license, title, contact, source links. The platforms section is the preferred way (since core24) to define build/run compatibility, architectures has been deprecated. Also, you can opt-out from tagging a packager repository, such as the JBang catalog repository. Gradle Some fixes to make the jreleaser-gradle-plugin be compatibile with Read More

JReleaser v1.25.0 has just been released! The full list of issues can be found at the v1.25.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Packagers Support multiple archive formats in jlink and native-image assemblers. You can now create ZIPs, TARs, at the same time. Signing Fixes to signing with PGP when specific options are missing. As always, feedback is welcomed, feel free to file a ticket or start a discussion topic. Keep on coding!

JReleaser v1.24.0 has just been released! The full list of issues can be found at the v1.24.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Packagers The Docker package now relies on multi-stage builds to generate smaller images. Chocolatey resource templates have been modernized. Announce Zernio is now supported as an announcer. You may use it to rely messages to multiple destinations. Core Reproducible artifact support has been enhanced by adding a flag that controls whether timestamps should be applied Read More

April 10th marks the anniversary of JReleaser’s first release. I’m ecstatic to announce JReleaser has reached 5 years since its first release and 4 since it posted its 1.0.0 release. The tool keeps posting releases like clockwork, every second month, on even months, at the end of the month. This means there are at least 6 releases per year. New features were added, making the tool more flexible and customizable. JReleaser can make the following claims in the last 12 months: The number of contributors has been raised to 109. The number of stargazers is now up to 1213. Tighter Read More

JReleaser v1.23.0 has just been released! The full list of issues can be found at the v1.23.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Version CHRONVER now accepts a lenient format. Time elements may or may not use a separator. For example, the following version strings "20260228" and "2026.02.28" both resolve to February 28th, 2026. Maven All Maven MOJOs now accept a generic jreleaser.skip property to skip their behavior, useful in multi-module builds where you’d like JReleaser to be Read More

JReleaser v1.22.0 has just been released! The full list of issues can be found at the v1.22.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Sign The signing section has been overhauled. You may now sign artifacts using multiple methods simultaneously. Also, minisign is now supported. Note that signing commits and deployments to Maven Central still required PGP signatures. Deploy Deploying artifacts to Maven Central required waiting for the deployment to be fully published before continuing the next step. Often Read More

JReleaser v1.21.0 has just been released! The full list of issues can be found at the v1.21.0 milestone. This is a small release with a handful of fixes and just a couple of new features. We’d like to thank our most recent contributors as well. Announce Release announcements may now be posted to Reddit. Reddit is the latest announcer added to the list of supported announce targets. Signing You may now use a GPG agent when signing artifacts. Additional updates and fixes when the signing mode is set to COMMAND. Release GitHub’s immutable releases are now supported. Be aware that Read More

JReleaser v1.19.0 has just been released! The full list of issues can be found at the v1.19.0 milestone. This release adds a new flag, yolo, that allows skipping misconfigured sections without breaking the release process. We’d like to thank our most recent contributors as well. Core The yolo flag allows JReleaser to skip a section that may be misconfigured or has missing information as secrets or tokens? Why would you want something like this? Say you have a generic release configuration for deployment, releasing, and package publication. There may be times when you just want to deploy to a Maven Read More

JReleaser v1.18.0 has just been released! The full list of issues can be found at the v1.18.0 milestone. This release adds support for Nexus3 as a Maven deployer. It also welcomes Forgejo as a releaser, uploader, and deployer. We’d like to thank our most recent contributors as well. Deploy Nexus3 becomes a supported deployer. There’s no supported for staged deployments for this deployer. The guide has been updated with sample code for deploying snapshot released to Maven Central. Release Forgejo may be used as a releaser, deployer, and/or uploader. Codeberg support has been migrated from Gitea to Forgejo. Package You Read More