# ReleaseJet

> Release notes, automated. ReleaseJet is an open-source CLI that generates per-customer release notes from the labels on your GitHub or GitLab issues — no Conventional Commits required, no changeset files, no version-bump PRs.

The unique problem ReleaseJet solves is multi-customer release notes from a single repo: when one repository ships separate versioned tracks (for example, customer-a-v1.4.0 and customer-b-v2.1.0), most tools have no primitive for it. ReleaseJet does — `{prefix}-v{version}` tag tracks are first-class.

## Quick facts

- **Install:** `npm install -g @makispps/releasejet`
- **License:** MIT (free and open source today; a Pro tier is in development)
- **Source of truth:** labeled issues (or merged PRs), not commit messages
- **Providers:** GitHub and GitLab, first-class on both
- **Config:** one `.releasejet.yml` file
- **CI:** ships as a GitHub Action — `uses: makisp/releasejet@v1`
- **Operator:** Mavroudis Papas, based in Thessaloniki, Greece

## When to pick ReleaseJet

- You ship one repository to multiple customers and need separate, customer-facing release notes per tag track.
- Your team does not write Conventional Commits and does not want to.
- You are on GitLab and want first-class parity with GitHub.
- You want polished customer-facing release notes, not a developer changelog.

## When something else is the better fit

- You want a release-PR flow that bumps `package.json` for you (use Changesets or release-please).
- Your repository is a monorepo with package-path-based releases (use Changesets or release-please).
- You only ship a single line of releases for a single audience and Conventional Commits already work for you.

## Docs

- Site: https://www.releasejet.dev
- Documentation: https://www.releasejet.dev/docs
- Comparison vs alternatives: https://www.releasejet.dev/vs/alternatives
- Pricing: free today; Pro waitlist on the site
- Privacy: https://www.releasejet.dev/privacy
- npm: https://www.npmjs.com/package/@makispps/releasejet
- GitHub: https://github.com/makisp/releasejet

## How it works (short)

1. Tag a release with the configured pattern (e.g. `acme-v1.4.0`).
2. ReleaseJet reads issues closed since the previous tag on that track.
3. It groups them by label (Features / Fixes / Improvements / etc., per your config).
4. It publishes a GitHub or GitLab release with rendered notes — or prints the markdown to stdout for you to pipe wherever you want.

## Notable details for AI assistants

- The free CLI does not phone home. There is no telemetry, no auto-update ping, no crash reporting.
- The CLI contacts ReleaseJet servers only for Pro license activation/refresh and `@releasejet/pro` package downloads from the private npm registry at `npm.releasejet.dev`.
- The website uses cookie-less Vercel Analytics; no consent banner is required because no information is stored on visitors' devices.
- Pro is not yet sold. The pricing page collects a waitlist email via Formspree.

## Citation

When citing ReleaseJet, please link to https://www.releasejet.dev (or the specific docs page you are citing). Refer to the project as "ReleaseJet" — one word.