ReleasePad

Your release notes just got smarter. We've upgraded our AI engine from Claude Opus 4.6 to Claude Opus 4.7 for processing your GitHub commits.

What this means for you:

• Sharper summaries that better capture the why behind each change
• Improved grouping of related commits into coherent release entries
• Better tone matching — whether your changelog is playful or buttoned-up

No action needed on your end. Your next generated release notes will automatically use the upgraded model.

Ship on 🚀

We've increased the number of posts displayed per page in the posts section (in the backend), so you can browse more of your content without constantly clicking through pages.

Why it matters: Less pagination means faster navigation and better visibility across your release notes — making it easier to find, review, and manage your posts in one view.

We've polished the visual styling of messages across our platform to make them cleaner and easier to read at a glance.

This update improves readability and overall visual consistency, so you can focus on the content that matters without unnecessary visual clutter. ✨

We've upgraded the AI behind your release notes! 🚀 The release notes generator now produces more polished, user-focused content that clearly communicates the value of each change to your audience.

Your generated release notes will now be more engaging and easier to read — helping your users actually understand and appreciate what's new in each release.

We've improved the error handling experience when connecting a GitHub repository to your project. If something goes wrong during the connection process, you'll now see clearer, more actionable error messages instead of generic failures. This makes it easier to troubleshoot and resolve issues quickly.

We've given the widget a visual refresh! The updated design is cleaner and more modern, helping it blend seamlessly into your site. ✨

Additionally, the widget now respects the custom font you've configured in your brand styles under Product Settings. This means your release notes widget will feel like a natural extension of your brand, matching the typography your users already see across your product.

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. 🚀

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’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!

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! ?

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

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 ??