Today, we released an update that fixes 2 bugs.

Subscriber import with invalid data

When our customers uploaded CSV files containing invalid or missing email addresses, they encountered a 500 error. Previously, our system incorrectly indicated that the file was fine and could be imported. We have now implemented checks to display an error if a name or email is missing, or if the email format is invalid.

Login via Google

In some cases, users were unable to log in or create an account using Google. Initially, we were unable to replicate this issue, but we have implemented a "blind" fix that should resolve it.

Today, we rolled out a routine maintenance update to upgrade the underlying software to their latest versions. Additionally, we resolved several minor bugs that were reported by our customers or detected in our error logs.

Possible breaking change (API)

We fixed the order in which entries are returned. Previously, entries were returned from oldest to newest. Now, they are ordered by the publication date. You can change/set this date when creating or editing an entry. This change also affects the order when using the ?limit=X parameter.

While you're reading this... we just released the public beta for a new product called tinydub. If you're curious, check it out.

Today, we released post reactions. Post reactions allow your readers to express their feelings about an entry using emoji expressions: happy, neutral, and sad.

The main navigation now features a new item, "Reactions." There, you can see a list of all reactions, with the newest shown at the top. Within the "Published" view, any entries having at least one reaction will show a default emoji that displays the count of all given reactions.

To enable reactions, head over to the workspace settings and enable "Post reactions". Reactions will be visible in the standalone changelog, and within widgets. Reactions can be changed, and also removed by the reader.

Consider this a v1. We do plan to extend this by optional comments, notifications and a chart in the dashboard.

Today, we released a maintenance update and also added an option to send emails via your own domain.

Custom email sender

We're pleased to announce that, due to popular demand, we are now offering the option to send emails using a custom domain. This is a paid add-on, requiring a one-time payment, and it is valid for all workspaces within an account.

After unlocking the add-on within the workspace settings, you will need to add a TXT and CNAME record to your domain. Simply follow the setup instructions. Once everything is verified, emails will be automatically sent from your own email address.

Maintenance and bug fixes

We updated all underlying software to their latest versions, fixed several bugs, and optimized a few database queries for better performance.

Today we added some minor updates to the API.

Add limit parameter

It is now possible to limit the number of entries when using the GET endpoint https://releasesapp.com/api/entries to fetch entries.

Simply add ?limit=X to the endpoint to fetch a limited number of entries.

Create entry

We also added a new endpoint that allows you to create entries via the API. The following parameters are allowed:

{
    "title": "The title of the entry",
    "slug": "the-slug-of-the-entry",
    "is_published": true,
    "publish_at": "2025-03-19",
    "notify_subscribers": false,
    "html": "<b>Hello there</b>"
}

It's currently not possible to assign tags or attach files via the API. Head over to the API Endpoints help center article to learn more.

Today we fixed a couple of smaller bugs and also added support for password-protected changelogs.

To restrict a workspace with a global password, head over to the workspace settings and scroll to the "Access" section.

We're happy to finally release our new editor. 🎉

After an extensive period dedicated to crafting the migration script to ensure existing posts are compatible with our new editor, we have finally achieved the desired outcome.

Following lots of testing, we have successfully migrated all content to the new format and are thrilled to announce the release of the new editor.

AI powered, if you need it

We're happy to introduce a subtle AI Assistant. You can ask the AI Assistant to write an article for you, or fix grammar, re-write, translate, shorten or extend text and much more.

The AI Assistant is available to all customers.

Code highlighting

To those posting code snippets, we also have great news. When adding a code block, or editing an existing one, you can now set the programming language (get in touch with us if you're missing anything). When viewing the article in the frontend, correct highlighting is applied and you can also copy code snippets.

public function envelope(): Envelope
{
    return new Envelope(
        subject: 'New team member signed up',
    );
}

Code highlighting is powered by Torchlight.

The editor looks and feels completely different and more modern. We hope you like it as much as we do. There may be a few smaller quirks that we need to fix over the next few days but it's already such an improvement to our previous editor. Let us know if you have any feedback or wishes.

One of the extensions that we used for our editor caused an issue with some inline formatting options such as bold and italic. While clicking these options, some web browers such as Chrome and Firefox submitted the entry because of a missing type="button" on those elements.

As a consequence, we removed the extension (it was the tooltip extension) to prevent any further issues. Sorry for the inconvenience and thanks for reporting.

As noted in the previous entry, we're currently working on a custom editor that will allow us to better customize all sorts of things and to implement our own logic and UI.

It has been somewhat quiet in the past couple of weeks, but that does not mean we're not working on new features and bug fixes. Not everything is worth publishing, although it would make our changelog look more active.

In the past weeks, we've regularly shipped maintenance updates and bug fixes, both within the backend and also for our themes.

What we're currently working on

We're currently working on a new editor, because the current one is partly broken (mainly in Safari) and kind of limits us when it comes to the UX and UI. We plan to launch the first version of the new editor later this month, along with a few other additions. Stay tuned.

Today we added the possibility to translate the system texts that are visible when using our widget. You can now set a custom headline (default is "Updates"), read more label and show all link text. Please note that those texts are uppercase by default, you cannot change that for now.

To update those texts, open the workspace general settings and find the section "Custom texts / translations". In the panel, scroll all the way down until you see "Widget".

Apart from maintenance work, today we released some optimizations for images. Before this update, images were not processed in the frontend, so when a 6000x4000 pixel image with 6.5 MB was uploaded, it was rendered like that in the frontend.

Those images were cached, so it was only somewhat slow on the first visit. Still, this could be improved.

Uploaded images are now much smaller by default and you can click on an image to see a bigger version of it, if available. This is enabled by default, nothing for admins to activate.

The same strong caching mechanism takes effect, so pages will load even faster now with a much more reduced network load time.

Nothing big, just two bug fixes in the email templates.

When using a custom logo for emails, some apps were showing the logo oddly shaped, not recognizing our custom styles. We tweaked this a little and logos should now have the correct proportions.

Another issue was the button in emails. Some vendors, such as Gmail, removed some of our custom styles, making the text barely readable. This should be fixed as well.