Skip to main content
Comparison

ReleaseJet vs the alternatives.

Most release-notes tools — release-please, semantic-release, changie— assume the same workflow: Conventional Commits or commit-derived fragments, monorepo packages, GitHub-only. Here's how ReleaseJet differs — and when one of them is the better pick.

Feature comparison

CapabilityReleaseJetrelease-pleasesemantic-release
Multi-customer tag tracks in one repoYes — first-class ({prefix}-v{version})No — monorepo packages, path-basedNo — single-package model
Works without Conventional CommitsYes — label-drivenNo — Conventional Commits requiredNo — Conventional Commits required
GitLab supportYes — first-classLimited — GitHub-firstYes — official GitLab plugin
PR-based release flowNo — tag-basedYes — release PRs are the signatureNo — commit-triggered on push
Version bumping in package.jsonNo — does not touch version filesYes — manifest-drivenYes — bumps and publishes
Config complexityLow — 1 YAML fileManifest + per-package configOne .releaserc + plugins
Source of truthLabeled issues (or merged PRs)Commit history (Conventional Commits)Commit history (Conventional Commits)

When ReleaseJet is the better choice

Pick ReleaseJet when:

  • You have one repo serving multiple customers and need per-customer release notes. Most alternatives have no primitive for this.
  • Your team doesn't write Conventional Commits and you don't want to start. We use labels on issues as the source of truth.
  • You're on GitLab— not every tool treats both providers as first-class; we do.
  • You want polished release notes, not developer changelogs — categorized, readable, customer-facing.

How to migrate

  1. Remove your current release-automation config files from the repo.
  2. Install ReleaseJet: npm install -g @makispps/releasejet.
  3. Run releasejet init to generate .releasejet.yml.
  4. Make sure your issues are labeled (categories like feature, bug, improvement per your config).
  5. Add a GitHub Action step:
    - uses: makisp/releasejet@v1
  with:
    tag: ${{ github.ref_name }}
    token: ${{ secrets.GITHUB_TOKEN }}
  6. Push a tag. Done.
Need more detail on any step?Read the full setup guide

Ready to
lift off?

Stop writing release notes by hand. Automate it in under a minute.

View on GitHub
Quick Install