Release notes, automated.
For multi-customer repos.
Per-customer release notes, generated from the issues your team already labels — no Conventional Commits, no changeset files, no PM chasing developers.
### New Features
- Multi-client repository support
- Smart milestone detection...
Any team where the PM owns the release story. You don't need multiple customers to benefit — you just need labeled issues and a PM who's tired of chasing developers.
Why ReleaseJet
Models customers, not packages.
The only release tool that understands “one repo, many customers.” Tag tracks per customer, filtered issues per customer, per-customer release notes.
See how we compareIssues → notes. No commit conventions.
Your team already labels issues. That's all we need. Skip the multi-month Conventional Commits migration. Skip the changeset-file discipline. Ship the notes your PM actually wants.
GitHub and GitLab, first-class.
The only release tool that treats both providers as equals. Same commands, same config, same output — whether you're on GitHub or GitLab.
How It Works
Configure
Run the init wizard. It detects your provider, sets up categories, and writes the config.
# creates .releasejet.yml
Generate
Point it at a tag. It collects issues, categorizes by label, and formats release notes.
Automate
Add one step to your CI pipeline. Push a tag and release notes get published automatically.
on: push: tags: ["v*"]
run: releasejet generate \
--tag $TAG --publish
Features
Multi-client Repos
Tag with client prefixes like mobile-v1.0 and web-v2.0. Each client gets its own release notes automatically.
Smart Categories
Map your labels to release note sections. Features, bugs, improvements — organized and formatted automatically.
CI/CD Ready
GitHub Actions and GitLab CI templates included. Trigger on tag push.
Rich Descriptions
The first paragraph of each issue or PR renders beneath its title. Context for readers, no extra work for you.
Jira Linking
PROJ-123 IDs in titles and bodies become live links automatically. No API keys, no plugins.
Issues or PRs
Source release notes from closed issues or merged pull requests. Same flow, either way.
RELEASEJET PRO.
The next evolution of release automation — built for teams that ship at scale.
- AI-powered release summaries
- Custom Handlebars templates
- Web dashboard with release history & metrics
- Slack, Discord & Teams notifications
- Outbound webhooks for Zapier, n8n & custom integrations
- Monorepo & multi-project support
Example
v1.1.0
Bug Fixes
- Fix crash when uploading zero-byte files (#43)
Uploader throws an unhandled exception on empty files instead of rejecting cleanly.
- Fix date picker off-by-one in Safari (#42) [BUG-147]
Safari renders the date picker one day behind due to timezone parsing. Sourced from Jira [BUG-147].
Improvements
- Cache avatars to cut dashboard load time (#44) [FEATURE-231]
Avatar images refetch on every nav. Add client-side caching with a short TTL. As discussed in Jira [FEATURE-231].
Other
- Rotate signing keys quarterly (#45)
Operational hygiene — rotate the JWT signing keys on a quarterly schedule.
Contributors
Everything above is generated from this repo's issues, labels, and .releasejet.yml. Fork it, run it, see the same output.