We Have a Changelog Now
Why bother
You're evaluating a tool and the last blog post is from six months ago. The landing page mentions "AI-powered" something. Is this thing still maintained? Is anyone home?
that's the vibe a product gives off when there's no public record of what's shipping. And honestly, we were in that spot. We've shipped a ton since January (SSL monitoring, heartbeat monitors, AI incident management, OG images) but unless you followed us on X, you'd have no idea.
What we built
A simple changelog page at getchirp.dev/changelog. It's a timeline feed showing what we've shipped, sorted newest first.
Each entry has a date, a category badge (feature or fix), a title, and a short summary. Click through for the full write-up. That's it. No complex CMS, no database tables. Just MDX files in the repo that get rendered at build time.
RSS if that's your thing
The changelog has an RSS feed at /changelog/rss.xml. If you use a feed reader (we see you, fellow nerds), you can subscribe and get updates without checking the site.
What's in there so far
We backfilled entries for the five biggest features we've shipped:
- Uptime monitoring with auto-incident creation
- AI-powered incident management (drafts, updates, post-mortems)
- Cron and heartbeat monitoring
- SSL certificate monitoring
- OG images for status pages
Going forward, every user-facing feature and notable fix gets a changelog entry when it ships. No more silent deploys.
What's next
We're working on a weekly email digest so registered users get a summary of what shipped that week. Opt-in by default, easy unsubscribe, nothing spammy. That'll be a separate update.
For now, bookmark /changelog or grab the RSS feed. If you're building something and want a status page that actually keeps improving, give Chirp a try.