Ross ROSS = Recommend OSS · open-source software intelligence for agents

jreleaser/jreleaser

:rocket: Release projects quickly and easily with JReleaser observed · 2026-08-28

github.com/jreleaser/jreleaser · homepage · Java · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

92/100

  • Activity 99
  • Release rhythm 78
  • Longevity 100

Flags: no_readme

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 61.0
  • age_days: 2104
  • days_rel: 65
  • days_push: 9
  • n_releases_24m: 11

Full methodology

Adoption not part of the score

1236 stars · 158 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

cli-tool · maturity stable

cli ci-cd deployment developer-tools developer-tools version-control jvm cli cross-platform 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

1 source

Member repositories

RepositoryRoleHealth v2
jreleaser/jreleasermain92

For agents

markdown · JSON · MCP: product_card(name="jreleaser/jreleaser")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem