# jreleaser/jreleaser

:rocket: Release projects quickly and easily with JReleaser

Repository: https://github.com/jreleaser/jreleaser
Canonical: https://ross.abutalabs.com/products/jreleaser
Homepage: https://jreleaser.org
Language: Java
License: Apache-2.0
License Family: permissive
Topics: java, release, maven, gradle, ant, cli, ci-cd, hacktoberfest, csharp, elixir, rust, tool
Last push: 2026-08-24T19:22:32+00:00

## Health v2 (maintenance only)
Score: 92/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 78, longevity 100
- inputs: {"age_days": 2104, "days_push": 9, "days_rel": 65, "gap_med": 61.0, "n_releases_24m": 11}
- flags: no_readme
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1236, forks 158 (observed 2026-08-28T04:04:05.242962+00:00)

## What it is
JReleaser is a release automation tool that tags and publishes releases to git hosting services like GitHub, GitLab, and Gitea, while generating changelogs, checksums, and PGP signatures for release artifacts. It packages applications for popular packagers (Homebrew, Scoop, Chocolatey, Snapcraft, JBang) and announces releases, running as a CLI, Maven/Gradle plugin, Ant task, JBang integration, or Docker image.

## Use cases
- automate tagging and publishing releases to github or gitlab
- generate a changelog from commits since the last tag
- publish my CLI app to homebrew, scoop, or snapcraft
- sign release artifacts with pgp and create checksums
- announce a new release to mastodon, sdkman, or zulip
- release a java, rust, go, or node project from CI
- upload release artifacts and distributions in one command

## When to choose
- you want end-to-end release automation (tag, changelog, sign, upload, package, announce) driven by convention over configuration
- your project uses Java, Go, Node, Rust, or similar ecosystems and you distribute via Homebrew, Scoop, Snapcraft, and alike
- you prefer running releases from the command line, Maven, Gradle, Ant, or a Docker image without writing custom CI scripts

## When to avoid
- your release pipeline has highly custom steps that do not fit JReleaser's conventions
- your build tool or CI already handles simple publishing and you do not need packaging or announcements
- you only need a one-off release and do not want to maintain a configuration file

## Facets
- artifact type: cli-tool
- maturity: stable
- function: cli, ci-cd, deployment, developer-tools
- domain: developer-tools, version-control
- platform: jvm, cli, cross-platform
- tags: release-automation, changelog-generation, pgp-signing, checksums, maven-plugin, gradle-plugin, homebrew, scoop, chocolatey, snapcraft, release-announcements, software-distribution, git-release, devops, automation, command-line, docker

## Member repositories
- jreleaser/jreleaser (main) score 92

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:05.242962+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:21:59.335199+00:00, confidence not recorded.
  - homepage: https://jreleaser.org (fetched 2026-08-29T12:21:14.455154+00:00, sha a07f4c8e64ae)
- Data as of 2026-08-30T08:39:29.467469+00:00.