Zero-touch publishing — release once, we ship the rest
The product's pitch and the product's behavior finally line up. Connect the GitHub webhook, flip to Zero-touch, and publishing a release on GitHub fires the entire downstream pipeline.
Preview
Zero-touch publishing — release once, we ship the rest
_2026-05-26_
The product's pitch and the product's behavior finally line up. If you connect the GitHub webhook and switch your project to Zero-touch mode, publishing a release on GitHub fires the entire downstream pipeline — the public page goes live, all confirmed subscribers receive the release in their inbox, Slack and Discord light up, and the owner gets a summary email. Zero clicks inside ReleaseNoteKit.
What's new
- Zero-touch mode — GitHub release → public page + email blast + Slack + Discord, automatically (#21)
- Auto-publish mode — middle ground: public page + Slack/Discord, but email blast stays manual for review
- Manual mode (default) — draft only, you publish like before
- 1-hour cooldown per project guards against runaway GitHub re-fires
- Confirmation modal before enabling auto-publish or zero-touch, with explicit warnings
Why this matters
Headway and Beamer still expect you to write a release post. ReleaseNoteKit now expects you to not. You ship to GitHub, customers find out the same minute, and you never opened a separate "release notes" tab.
Safety
- Owner gets a summary email after every auto-fire ("v2.1.0 shipped — 38 subscribers notified, posted to Slack")
- Cooldown blocks duplicate fires inside an hour
- AI output review is one click away from the dashboard if anything looks off
Pro plan only. Existing Pro projects upgrade automatically.
Markdown
# Zero-touch publishing — release once, we ship the rest
_2026-05-26_
The product's pitch and the product's behavior finally line up. If you connect the GitHub webhook and switch your project to **Zero-touch** mode, publishing a release on GitHub fires the entire downstream pipeline — the public page goes live, all confirmed subscribers receive the release in their inbox, Slack and Discord light up, and the owner gets a summary email. Zero clicks inside ReleaseNoteKit.
## What's new
- **Zero-touch mode** — GitHub release → public page + email blast + Slack + Discord, automatically ([#21](https://github.com/zbfs2cgh2h-sketch/releasenotekit/pull/21))
- **Auto-publish mode** — middle ground: public page + Slack/Discord, but email blast stays manual for review
- **Manual mode** (default) — draft only, you publish like before
- 1-hour cooldown per project guards against runaway GitHub re-fires
- Confirmation modal before enabling auto-publish or zero-touch, with explicit warnings
## Why this matters
Headway and Beamer still expect you to write a release post. ReleaseNoteKit now expects you to *not*. You ship to GitHub, customers find out the same minute, and you never opened a separate "release notes" tab.
## Safety
- Owner gets a summary email after every auto-fire ("v2.1.0 shipped — 38 subscribers notified, posted to Slack")
- Cooldown blocks duplicate fires inside an hour
- AI output review is one click away from the dashboard if anything looks off
Pro plan only. Existing Pro projects upgrade automatically.
Tweet / X thread
🚀 ReleaseNoteKit 2.1.0 is out. Release once. We ship the rest. GitHub release → public page + email blast + Slack + Discord, automatically. Zero clicks inside ReleaseNoteKit. --- Three modes, per project: • Manual — draft only, you publish (default) • Auto-publish — page + Slack/Discord, email stays manual • Zero-touch — full automation, summary email after --- Guardrails: • 1-hour cooldown per project (no runaway re-fires) • Confirmation modal before enabling • Owner summary email every auto-fire --- Pro plan only. Existing Pro projects upgrade automatically. Full changelog → https://releasenotekit.toolu.dev/examples/releasenotekit
Email digest
Want this on your own repo?
Free preview, $19 once to publish. No subscription.