JReleaser

jreleaser.org ↗

Prepare and publish software releases across Git hosts and package managers.

SI Score
75/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about JReleaser

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the JReleaser homepage

What it does

JReleaser automates release work for Java and non-Java projects. It can create Git releases with tags, changelogs, and assets; assemble files for package managers; and announce releases. It runs locally or within an existing CI system, complementing rather than replacing build tools and CI platforms.

Start after a build has produced the artifacts you intend to ship. Configure JReleaser through its CLI configuration file or a Maven, Gradle, or Ant integration, then supply the artifacts and target Git host or package managers. For example, a Java library release might use the built JAR and source archive to prepare a tagged Git release, changelog, and distribution files. The expected output is release metadata and prepared assets, not a compiled application.

The project is adjacent to GoReleaser, which inspired it, but JReleaser documents support for Java and non-Java projects and integrations with Java build tools. Changesets focuses on contributor-declared version and changelog updates, particularly in monorepos; JReleaser focuses on assembling and publishing releases. Existing CI tools such as GitHub Actions, GitLab CI/CD, or Jenkins can invoke it as one release step. Credentials and destination-service configuration remain part of the team's setup.

Strengths

  • Handles several release stages, including Git releases, package-manager distributions, and announcements.
  • Supports Java and non-Java projects, with integrations for common Java build tools.
  • Can run within existing CI rather than requiring a replacement CI platform.

Watch out for

  • Release configuration and destination credentials remain the operator's responsibility.
  • It is a release tool, not a build system or general-purpose CI service.

Best for

  • Projects publishing release assets to multiple Git hosts or package managers
  • Java projects that want release automation integrated with their build tooling
  • Teams using an existing CI platform that need a dedicated release-automation step

Sources