JReleaser v1.0.0-RC2 has just been released! There were 2 issues reported against v1.0.0-RC1. Remember that all deprecated code has been removed, we recommend upgrading to 1.0.0-M3 first to find out if your build uses deprecated features before moving to 1.0.0-RC2. As always, feedback is welcomed, feel free to file a ticket or start a discussion topic. Keep on coding! Image by Kien Virak from Pixabay
JReleaser v1.0.0-RC1 has just been released! There’s only a handful of small fixes to be found in this release. However, the main change is the removal of all deprecated code. We recommend upgrading to 1.0.0-M3 first to find out if your build uses deprecated features before moving to 1.0.0-RC1. This is it. We’re on the home stretch to v1.0.0! Barring any blockers this means v1.0.0 should hit the streets in a couple of weeks. We simply could not have done it without the feedback we’ve received from early adopters. Thank you so much! As always, feedback is welcomed, feel free Read More
JReleaser v1.0.0-M3 has just been released! The third milestone release (likely the very last one) towards 1.0.0 is here! This release fixes several issues found in assemblers (jlink, jpackage, native-image). The v1.0.0-M3 milestone shows all closed tickets. Here’s a quick summary of what’s changed: Jlink Support for creating custom Java runtimes for modular applications has been revamped. JReleaser did not handle paths and quoted arguments correctly when running on Windows, that’s now a thing of the past. JPackage Both appName and appVersion properties now support name templates. You may also override appName per platform. Building packages for modular applications is Read More
JReleaser v1.0.0-M2 has just been released! The second milestone release towards 1.0.0 is here! This release fixes a variety issues find by users. Be mindful of the breaking changes introduced in this release. There are no big features added in this release, just a handful of improvements and plenty of fixes, such as Chocolatey Lots of improvements in this area such as GitHub workflow files being placed at their correct location; POSIX file permissions handled correctly when running on Windows; skip remote repository when packaging on Windows; simplified templates for BINARY and NATIVE_IMAGE distributions; ability to override package version; validate Read More
JReleaser v1.0.0-M1 has just been released! This is it folks, the road to v1.0.0 has just begun! This release fixes a variety of small issues found by consumers. Be mindful of the breaking changes introduced in this release. There are just a handful of new features besides all fixes, such as Sigstore Cosign Artifacts may now be signed with Sigstore’s cosign. JReleaser will download a cosign binary if there’s none available on the system. Cosign signatures are not compatible with GPG and thus can’t be used to sign commits and tags. Native Image Native executables created with GraalVM Native Image Read More
The year 2021 is now behind us and what a year it was. Sometimes I could not keep listening to the news, once you feel the grip of depression you must act quickly to get out of the downward spiral. When that happened I turned my attention to code. Fortunately at work together with my teammates we had a series of success stories and wins all year long, yay for us! Now on the side of personal projects I did not manage as many releases as last year, 59 this years vs. 98 last. Or did I? Back in late Read More
You’ve spent some time working on that Rust project of yours and are now ready to post a release. It’s quite straight forward to build and upload binaries as assets to a Git release but let’s face it, we can’t expect consumers to find the release page, select the appropriate binary for their platform, download the file, and configure their environment settings to point to the new binary. Well yes, some people like to do that but most prefer to use a tool instead, something that automates the steps just described, something like a package manager such as Homebrew, Snapcraft, Read More
JReleaser v0.10.0 has just been released! It is the last push towards 1.0.0. We’ll concentrate on bug fixing and polishing from now on. Be mindful of the breaking changes introduced in this release. There are plenty of improvements in several areas, a quick summary of the highlights follows: JPackage The jpackage tool can now be used to assemble distributions of type NATIVE_PACKAGE. You have the choice to reuse an existing jlink assembler or supply a runtime image created by any other means. Archive Extensions Additional archive extensions are now supported, such as .tar.xz, .txz, tar.bz2, .tbz2, with most packagers and Read More
JReleaser v0.9.1 has just been released! This is our first fix point release as a bug fell through the cracks preventing distributions of type NATIVE_IMAGE to be successfully assembled using JReleaser’s Native Image assembler or just packaged with any of JReleaser’s supported packagers. We encourage everyone that has moved to v0.9.0 and requires NATIVE_IMAGE support to upgrade to v0.9.1 at your earliest convenience. There are also a couple of additions in this release (full list of changes found here): CalVer Because there’s more than one way to version your project and sometimes SemVer is not enough, CalVer is now also Read More
🚨 UPDATE 🚨 Please upgrade to v0.9.1 instead! JReleaser v0.9.0 has just been released! JReleaser v0.9.0 is a big update as we gear towards v1.0.0. Plenty of improvements were added to this release to make it the best one so far. Be mindful of the breaking changes introduced in this release.There are plenty of improvements in several areas, a quick summary of the highlights follows: Jlink We’ve made several improvements to the Jlink assembler. In particular it’s now possible to create a Jlink image for Quarkus applications using their fast JAR layout. You’ll find an example at the project’s documentation. Read More