JReleaser
JReleaser is a release automation tool for developers shipping Java or non-Java software who need reliable packaging, publishing, and release announcements…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
73/100 Good
- Maintained
- 93last commit 21 days ago
- Popular
- 621,250 GitHub stars
- Easy to install
- 352 install platforms, install notes
- Light to run
- No data
- Security check
- 85no serious findings, CI, tests, OpenSSF Scorecard 7/10
Based on 4 of 5 factors.
- GitHub stars
- 1,250
- Open issues
- 129
- Last commit
- 2026-10-31
- Latest release
- v1.27.0
- License
- Apache-2.0
- Activity
- rising
Checked yesterday - source: GitHub (jreleaser/jreleaser)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install JReleaser with the setup script On Linux or macOS, open a terminal and run the setup script command shown in the docs. Without this step, the JReleaser tool is not installed, so you can't run the release process. source
- Point your config at real file paths Create your JReleaser config file (the instructions that tell it what to release) in JSON, XML, or a similar format, and put the exact file paths to the packages you want to release. If the paths are wrong, JReleaser can fail or release the wrong files. source
- Keep Docker registry passwords outside files If you publish a Docker image (a packaged copy of your app for Docker), put the registry password in an environment variable (a secure setting outside your code) and set the repository name, which is the place in the registry where the image should go. This keeps secret passwords out of your project and helps the image go to the right place. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need a setup step to install JReleaser on Linux or macOS?
Yes, open a terminal and run the setup script command shown in the docs, because the release process cannot run without the tool installed.
What configuration mistake can cause JReleaser to fail or release the wrong files?
The config file must point to the exact file paths of the packages to release, because wrong paths can make JReleaser fail or publish incorrect files.
Which software packagers can JReleaser use for distribution?
JReleaser can package your application for distribution with packagers such as Homebrew, Scoop, Chocolatey, and Snapcraft.
Answers sourced from jreleaser.org, jreleaser.org, jreleaser.org
Community
- JReleaser says hello! : r/java - Reddit (reddit)
- JReleaser 1.0.0 is here! : r/java - Reddit (reddit)
- Recently Active 'jreleaser' Questions - Stack Overflow (forum)
- Options to replace self hosted Jira : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads