We resolved a bug where the created_at timestamp was not being read correctly from the cache layer. This could have caused incorrect dates to appear in certain areas of the application. ⏰
Timestamps are now parsed and displayed accurately, ensuring consistent and reliable date information across the platform.
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. 🎉
You now have full control over how your AI-generated release notes are written! We've added a new AI Settings panel where you can tailor the output to match your brand voice and audience preferences.
These settings are automatically applied every time new release notes are generated from your commits. Head over to your product's settings page to configure them.
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.
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:
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:
📊 📊 📊 📊
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
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 🎯
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. 👨💻
We've fine-tuned the line spacing in changelog posts so your content feels more cohesive and easier to scan. Previously, paragraphs could appear a bit disconnected with excessive vertical space between lines — now everything flows together naturally 📖
This subtle adjustment reduces padding and brings your release notes closer together without feeling cramped, making the overall reading experience cleaner for your users.
We've added a new display option that lets you place your widget as a sleek, minimized tab that sits along the edge of the page. Visitors can click the tab to expand and interact with the widget.
To use, just add widget-position="right" (or left) on your widget initialization code (see below for an example).
<div id="rp-widget" class="rp-container"
data-param="SFMyNTY.g2gDYYhuBgCDM3qEmgFiAAFRgA.t92-Lw1A04pdEzpnzFWGd_yjbKpKrK7Pa3AARGc_Www" lang="en"
data-user-metadata="" widget-style="tab" widget-position="right" widget-label="What's new" enable-animation="true"
preview='true'>
</div>Once you do you should see something like this:
We identified and resolved an issue that was causing incorrect post counts to display on the products index and individual product public pages.
What was happening: The number of posts shown for each product wasn't reflecting the actual count, which could lead to confusion when browsing products or viewing product details.
What we fixed: We corrected the query logic responsible for calculating and displaying post counts. Products now accurately show the correct number of associated posts across both the products listing page and each product's public page.
No action required — this fix has been automatically applied.
We identified and fixed a bug that was causing some post views to go uncounted. Previously, certain views weren't being recorded properly, which meant the view counts you saw were lower than your actual reach. 📉
What happened: A tracking issue was preventing views from being logged under specific conditions, resulting in underreported numbers across the platform.
What we fixed: Views are now being captured correctly. Your post view counts should reflect a more accurate (and likely higher) picture of your audience engagement. 📈✨
No action is needed on your part—the fix has already been applied. If you notice your view counts looking healthier than before, that's why. 🎉
We’ve shipped an improvement that makes the widget faster and easier to use 🚀. In addition to the speed boost, release notes are now visible directly in the widget index 📝—so you no longer need to open each post to see what’s new.
Less clicking, quicker updates, and a smoother experience overall ✨✅
We've been heads-down on improvements you won't directly see—but you'll definitely feel.
Performance upgrades mean faster load times and smoother interactions throughout the app.
We've optimized database queries, reduced payload sizes, and fine-tuned our caching layers.
Code quality improvements make us more reliable and nimble. We've refactored legacy code, improved error handling, and expanded our automated testing coverage—all of which means fewer bugs and faster feature development ahead.
Not the flashiest update, but this foundation work matters. It's what lets us build better, move faster, and keep your experience rock-solid.
🪨
We’re excited to announce the launch of our upgraded dashboard, designed to enhance your experience with greater flexibility and insight!
It now shows your public changelog page visits, total post views and published posts.
On the posts listing page, we’ve added a handy new filter that lets you easily search for posts that haven’t been published yet—basically, any post with a publish date set in the future. Now you can keep track of your upcoming content with just a few clicks!
Drafts Are Now Truly Private
We discovered that posts you marked as drafts were still appearing publicly—yikes, that’s not what anyone wants! We’ve fixed this issue, so your drafts stay hidden until you’re ready to share them with the world.
Blurbs That Capture Every Word
Some of you noticed that the short descriptions of your posts—your blurbs—were getting cut off, leaving out key words. That’s not fair to your story. We’ve resolved this, ensuring your blurbs now display every word as intended.
Today marks more than just a product release.
It’s the result of countless hours, late nights, breakthroughs, setbacks, rewrites, and relentless passion. We’re not just unveiling a new UI. We’re not just shipping a new backend. We’re giving you the experience we’ve always believed you deserve.
Every pixel, reimagined.******** We didn’t just give the interface a fresh coat of paint. We started from scratch. We listened to your frustrations, studied your workflows, and sweated over the tiniest details. The new UI is faster, clearer, and more intuitive—designed to disappear so you can focus on what matters. Every line of code, rebuilt.******** Behind the scenes, we tore down the old architecture and rebuilt it from the ground up. The new backend is faster, more stable, and ready for everything ahead. You may not see it—but you’ll feel it: in the speed, in the reliability, in the way everything just works. This is more than a launch. It’s a promise. To build with heart. To listen when it’s hard. To never settle. We built this for you. For the creators, the doers, the believers who never stop pushing forward. And this is just the beginning. Let’s go. 🚀
When creating a new post and adding new image, an incorrect placeholder image was being used.
This has been fixed ;-)
Fixed an issue that was preventing image load on both the widget and public page change log.
We added a new CDN to our platform that delivers your images and videos way way faster.
ReleasePad was very fast and now is extremely fast! ?
Today we had an outage because of a problem we had with one of our SSL certificates.
This has been fixed ?
We've been very quiet lately, but it doesn't mean we haven't been hard at work.
Currently finalizing the new version of the API which is 10X faster. That change will bring 2 big advantages for your product:
1.It will run extremely fast, that means you will get your work done even faster.
2.Since SEO is so important and you can get penalized when your website doesn't load in a reasonable amount of time, the new Widget will load 10X faster. Not that our current widget is not fast enough. It is ! But we wanted to raise the bar again and make it faster so we don't compromise your product or website.
Stay tuned !
We’ve brought back the ability to delete posts, and it’s ready for you to use! You can now find this feature right within the post editing section, making it super easy to remove any post whenever you need to.
When the widget loads for the first time in your product you will notice that it has a very subtle animation.
If you find it distracting, it can be easily disabled by adding the following tag to the widget:
enable-animation="false"
For more information, you can refer to the following article
https://help.releasepad.io/article/8-how-to-disable-widget-animation
They say that data is knowledge and knowledge is power.
This new feature that we are releasing today is going to give you a lot of data, knowledge and power to make decisions.
It will allow you to know which user have seen each one your posts.
Unfortunately this implementation only works for new post views since today and you must add an extra parameter to the widget.
This is what you need to do:
Step 1. Make changes in your widget.
Here is a quick step by step on what you need to do.
https://help.releasepad.io/article/6-how-to-enable-option-to-know-who-views-your-posts
**Step 2.** Find the posts you would like to know more about and click "Who has seen my post?". It's important to note that this information will be available only for the post views after performing step #1 **Step 3.** See your data.
The notifications bubble indicator on widget was being reseted after a couple of days. What this meant for end user were false alerts about new changes.
This has been fixed :-)
In the widget and public page, posts were displaying the creation date instead of the publish date.
This has been fixed and pushed.
Thanks Diana for noticing this :-)
In some special conditions, the words of some posts were overflowing to the left, creating an unpleasant experience for your users.
This has been fixed.
Improved the responsiveness of ReleasePad for mobile phones.The experience has been improved so that it loads faster and screens are rendered correctly based on device.
This morning we had some intermittency on our service. This was related to a change that Amazon AWS did on Cloudfront.We got in touch with support and managed to solve the issue.
In some special cases there were some css conflicts between the widget and the hosting page, particularly with headings (H1, H2, H3, ...).
This issue has been fixed and pushed.
Pushed a change that fixes the ordering of the posts. Instead of using the creation date it now uses the publication date.
We were having some issues with the current way of storing data for the user facing widget (the one you use on your product) related to local storage. Some logout implementations usually delete all local storage, therefore erasing all the widget data. This caused that each time a user logged out and the logged in it would appear as if it hasn't seen any of the updates, therefore creating confussion.
We switched to cookies to fix this issue.
For privacy matters it only stores the id from last seen post.
We updated our CDN provider for a faster one and with edge locations all around the world. This means that when a user loads the widget it will be sent form its closest physical location, therefore reducing loading times and latency ??
Fixed an issue that wasn't correctly displaying the number of published posts. It was taking also in account the number of drafts.
Pushed fix that opens all posts (from the widget) in a separate window.
Fixed an issue that was preventing images from being displayed correctly on the widget.
Fixed issue that was preventing the correct image upload in a new or existing post.