We resolved a bug that was preventing posts created via Git commits from being published successfully. The issue was related to how bullet point items in commit messages were being processed, which could cause the publish step to fail silently.

If you previously experienced issues with posts not appearing after pushing commits, everything should now work as expected. 🎉

We've lowered the commit threshold required to trigger automatic release note generation. Previously, you needed multiple commits before notes would be created — now, even a single commit is enough to kick off the process. This means faster, more timely release notes for smaller updates and quick fixes. 🚀

Stay in the loop with your release notes workflow! 🚀 When you push to your connected GitHub repository, ReleasePad will now automatically send you an email notification if any draft posts were generated from your commits.

This makes it easy to review and approve new release notes right away, so your changelog stays up to date without you having to constantly check for new drafts.

We fixed a bug where search filters and parameters were lost when navigating to the next page of results. Now your search criteria are properly preserved across all pages, so you can browse through filtered results without losing your query. 🔍

You can now exclude specific commits from your release notes by adding a [skip] tag anywhere in the commit message. This gives you full control over which changes make it into your polished release notes. 🎯

This is perfect for keeping internal housekeeping — like formatting fixes, refactoring, or CI tweaks — out of your user-facing changelogs.

• Add [skip] (case-insensitive) to any commit title or body to exclude it from release notes
• Skipped commits are still stored for your records, but won't appear in generated notes
• Works automatically — no extra configuration needed

Every time you push code, your users should know about it — but let's be honest, writing release notes after a deploy is the task everyone skips. Not anymore.

ReleasePad now connects directly to your GitHub repository. Once linked, every push triggers an automatic reading of your commits. Our AI then analyzes those commits and generates well-written, clear posts — categorized exactly how you've set them up — and publishes them to your changelog without you lifting a finger. 🔥

Here's what this actually means for your workflow:

• You push code. That's it. ReleasePad handles the rest.
• AI reads and understands your commits, then transforms raw technical messages into polished, user-friendly posts.
• Each post gets assigned to the correct category (features, fixes, improvements — whatever you've defined).
• Multiple posts get created from a single push if the changes span different areas of your product.
• Your users stay informed in real time, every single time.

Why this matters more than you think — the gap between shipping and communicating is where user trust erodes. Your team ships fast, but if your customers don't see those improvements, they assume nothing is changing. This integration closes that gap permanently.

No more deciphering commit messages into human-readable updates. No more "we'll write the changelog later." No more backlog of undocumented features. The AI does the heavy lifting — turning fix: resolve null pointer in auth flow into something your users actually want to read. 🧠

Connect your repo once, keep pushing code, and let your product speak for itself ✨

Ready to set it up? Inside your product, go to More → GitHub Integration → Add Repository — and you're good to go.

Stay on top of how your products are performing! We've introduced a new Weekly Stats Email that lands in your inbox every Monday morning, giving you a quick snapshot of the past 7 days.

Here's what's included in your weekly digest:

• Page views — See how much traffic your product pages received
• Post views — Track engagement on your release notes and announcements
• New posts — A summary of content published per product

📊 📊 📊 📊

Your public changelog pages just got a lot smarter — literally. We've added the ability to serve your changelog content in plain Markdown format, making it trivially easy for Large Language Models (LLMs) and AI agents to parse, understand, and act on your release history.

🔬 How it works?

Simply append ?markdown=true to any Releasepad public changelog URL:

https://pro.releasepad.io/en/your-product?markdown=true

The response comes back as text/markdown with a clean, structured format:

# Product Name Changelog
Website: https://yourproduct.com
Total Posts: 47
---

## New Feature: Dark Mode Support
**Category:** Feature
**Published:** Jan 13, 2026 at 02:30 PM
We've added full dark mode support across the dashboard...

---
Page 1 of 5
Next page: /en/your-product?markdown=true&page=2

🔗 Automatic Discovery

We've implemented the <link rel="alternate" type="text/markdown"> tag in the HTML head of every changelog page. This follows the same pattern as RSS feed discovery, allowing LLMs and crawlers to automatically detect the machine-readable version without any manual configuration.

💥 Why This Matters

Building an AI assistant that needs to know what changed in your product? Writing automated scripts that summarize releases? Feeding changelog data into RAG pipelines? Now your changelog is a first-class data source for any AI workflow.

Pagination is fully supported — LLMs can crawl through your entire release history page by page, with clear navigation links in the Markdown output.

💻 Technical Details

  - Content-Type: text/markdown; charset=utf-8

  - Caching: Same 6-minute public cache as HTML pages

  - All block types supported: paragraphs, headers, code blocks, ordered/unordered lists, images, and embeds

  This is part of our ongoing effort to make ReleasePad the most integration-friendly changelog platform out there. Your release notes shouldn't be trapped in HTML — they should flow wherever your users (human or otherwise) need them. 🤖

Bullet points and numbered lists in your release notes were breaking visually — that's now sorted. Whether you're outlining features, listing bug fixes, or breaking down steps, your lists will display correctly with proper indentation and spacing.

Write structured content with confidence knowing it'll look exactly how you intended 🎯

1. Item 1
2. Item 2
3. Item 3

• Item 1
• Item 2
• Item 3

Enjoy!

You can now include code snippets directly in your release notes! When writing technical updates, simply add code blocks and they'll render with a clean monospace font, subtle gray background, and proper formatting.

<div>
 // Some HTML Code here
<div>

Perfect for sharing API changes, configuration examples, or any technical details your users need to copy-paste. No more awkward workarounds to show code in your changelogs. 👨‍💻