HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
makisp
releasejet
TypeScript2026–2026
makisp / releasejet

releasejet

Automated release notes from issues and PRs between Git tags. Supports GitLab and GitHub.

Command LineWeb DevelopmentProductivityDeveloper ToolsDevOps & CloudAutomation & Workflows
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
12GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Automated release notes from issues and PRs between Git tags. Supports GitLab and GitHub.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2026-04-21 12:04:02 UTC to 2026-05-06 22:00:13 UTC.

012026-04-21 00:00:00 UTC to 2026-04-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 212026-04-22 00:00:00 UTC to 2026-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-23 00:00:00 UTC to 2026-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-24 00:00:00 UTC to 2026-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-25 00:00:00 UTC to 2026-04-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-26 00:00:00 UTC to 2026-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-27 00:00:00 UTC to 2026-04-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-28 00:00:00 UTC to 2026-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 282026-04-29 00:00:00 UTC to 2026-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-30 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-02 00:00:00 UTC to 2026-05-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-03 00:00:00 UTC to 2026-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-04 00:00:00 UTC to 2026-05-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-05 00:00:00 UTC to 2026-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-06 00:00:00 UTC to 2026-05-07 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 6

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 212026-04-21 00:00:00 UTC2026-04-22 00:00:00 UTC101
Apr 222026-04-22 00:00:00 UTC2026-04-23 00:00:00 UTC000
Apr 232026-04-23 00:00:00 UTC2026-04-24 00:00:00 UTC000
Apr 242026-04-24 00:00:00 UTC2026-04-25 00:00:00 UTC000
Apr 252026-04-25 00:00:00 UTC2026-04-26 00:00:00 UTC000
Apr 262026-04-26 00:00:00 UTC2026-04-27 00:00:00 UTC000
Apr 272026-04-27 00:00:00 UTC2026-04-28 00:00:00 UTC000
Apr 282026-04-28 00:00:00 UTC2026-04-29 00:00:00 UTC000
Apr 292026-04-29 00:00:00 UTC2026-04-30 00:00:00 UTC000
Apr 302026-04-30 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 12026-05-01 00:00:00 UTC2026-05-02 00:00:00 UTC000
May 22026-05-02 00:00:00 UTC2026-05-03 00:00:00 UTC000
May 32026-05-03 00:00:00 UTC2026-05-04 00:00:00 UTC000
May 42026-05-04 00:00:00 UTC2026-05-05 00:00:00 UTC000
May 52026-05-05 00:00:00 UTC2026-05-06 00:00:00 UTC000
May 62026-05-06 00:00:00 UTC2026-05-07 00:00:00 UTC110

What Hacker News says

2 sources
makisp·Apr 21, 2026
Hello HN, I'm Makis. For years I've maintained codebases we ship to multiple customers on independent version tracks, and writing release notes by hand has been a pain. I built ReleaseJet to automate it. There are existing tools for this (semantic-release, release-please, changesets) but none of them tackled our two problems: 1. We never adopted Conventional Commits. Our team labels issues and PRs, but we don't bother policing commit messages. All the existing tools assume the opposite of what we do. 2. We have one repo, many customers. We ship to many customers using independent tags (e.g., client1-v1.4.11, client2-v2.9.2). All other tools assume you have a single linear version history. ReleaseJet reads your Git tags, pulls the closed issues (or merged PRs) between the current tag and the previous one on the same client track, gro
Read the rest
ups them by a label → category mapping from a YAML file, and publishes formatted release notes to GitHub Releases or GitLab. - GitHub + GitLab, issues or PRs - Multi-client tag tracks out of the box - 5-line GitHub Action on the Marketplace - Free forever for public OSS repos Live demo with three customer tracks and real published release pages: https://github.com/makisp/releasejet-demo-multi-customer/rel... It's free and open source on GitHub: https://github.com/makisp/releasejet (MIT) I genuinely want to hear what's missing, what's broken, or how you've solved this differently.
In ReleaseJet – Release notes from issue labels, no Conventional Commits

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.