Feature

Today we launched the possibility to add custom scripts to workspaces. So if you want to integrate a third-party analytics tool, or a chat widget you can do this now within the workspace settings. Find the new nav item "Third-party scripts".

Please note that we are monitoring added scripts. If you add any kind of malicious scripts, we reserve the right to remove those and may also restrict your account.

We also added an option to set tooltips in the editor, like this one. It's a small addition that was requested 4 times already so... there you go. :)

Having the possibility to add files to entries was a common request from our customers, and we're happy that v1 of this feature is now live.

File uploads for releases

Files can now be added to entries. There is currently no limit how many files can be added, but the file size is limited to 30 MB per file (that should be enough for most cases). We may increase this limit at some point.

You may also add an external url if your file is already hosted elsewhere.

If you have feedback regarding file uploads, feel free to get in touch via the in-product chat.

Hide subscribe button

Another common request was to have a way to hide / disable the "Subscribe" button. That's now a new setting within the global workspace settings (look for "Enable subscription"). It's enabled by default, so if you don't want people to subscribe to changelog updates, just disable this.

We also fixed a couple of bugs and updated the underlying software to their latest versions.

It is now possible to hide the workspace name from the "Commit" theme. This option is visible when you select the "Commit" theme in the appearance settings. 

Multiple teams for accounts

It is now possible to belong to more than one team. Prior to this update, an account could not be part of multiple teams, only one team.

This one has been requested a couple of times and we're happy to finally introduce the possibility to add subscribers via CSV import. Import via API was already possible since we launched our API last September but a more convenient way was to directly upload them via the backend.

It is now possible to update system texts that appear within themes and emails.

You can now also change the default locale per workspace. The correct locale is important for many aspects, such as SEO. Search engines use language metadata to index and display search results in the appropriate language, enhancing discoverability and relevance.

To update or translate our default texts, go to your workspace settings (releasesapp.com/settings) and find the section called "Custom texts / translations". So changelogs can be fully translated into any language.

Removing the "Powered by" backlink

Having a backlink to Releases is important for us to spread the word about our platform. But we understand that some customers don't want this "Powered by Releases" visible on their changelog and widget. And that is totally fine, of course.

We made a change today that would lock the possibility to disable the backlink freely. Starting today, the backlink can be removed for a small one-time fee. While we understand that this may frustrate some customers, we made the decision to keep this at a one-time fee. It is common practice that a "Powered by" can be removed on higher-priced plans (we don't have any) or via a monthly payment.

We hope you understand this change. If you have any questions, you may contact us directly within the platform now.

Today we implemented a small feature that many of our early customers asked for: Tag filter.

It is now possible to click on a tag and see all entries with that specific tag. It is currently not possible (and not planned) to combine multiple tags to filter, only one tag at a time.

Want to keep track of subscribers and team signups via webhook? Well now you can. Today we added the possibility to get a POST webhook notification whenever someone subscribes or unsubscribes to your changelog. You will also be notified when someone joins your team, in addition to an email notification.

Email notifications for team signups can now optionally be disabled, but we suggest to keep them enabled.

Webhook notifications are automatically enabled once you add a valid endpoint to your workspace settings. To learn more about handling webhook requests, check out our help article.

"I need multiple workspaces" was something we heard a few times the past couple of weeks – mostly from our beta testers. Fair enough. This was something we had planned to build anyway, so we moved it up the todo list.

Additional workspaces are now available. Each account (except team member accounts) can create up to 3 workspaces by default. If more than 3 workspaces are needed, additional ones are available via a one-time payment of €5 (~ $5.30).

Workspace logo in backend

We also added the custom workspace logo to the backend view, if one was uploaded. This will replace our default "Releases" logo with the one from your own changelog. Dark mode and light mode versions are respected, if both were uploaded.

Today we added the possibility to sign up / sign in to Releases via Google and GitHub. Simply authenticate with your existing credentials and you are good to go. We may add additional providers in a future update.

We are excited to announce the introduction of "Teams". With this release, admins can now form and manage teams of any size.

Each workspace can have one team. There are no limitations on how many people can join a team – invite as many as you have. Invites are done via a unique invite-link that can be re-generated or disabled at any time.

Anybody with access to a workspace invite-link can join this workspace. Admins will be notified via email when a new member joined. There currently is no permissions or roles system in place. Only admins can remove members from a team.

In a future update, we may introduce a simple permissions / roles system that allows admins to define publish and delete rights to entries for specific users. Right now, every member of a team can publish and delete entries, has access to tags, subscribers, as well as to the workspace settings.

Today we would like to introduce a new feature called "GitHub Sync". If you keep your release notes on GitHub, changes are you have an open source package, an app or website or essentially anything that can be hosted on GitHub and shared with others.

Not everyone is on GitHub though. If you have a website, you can make use of our widget to show your release notes directly where your users are. Just keep updating your releases notes on GitHub and sync them with Releases anytime you like.

In a future update, we will add the option to auto-sync release notes. "GitHub Sync" is currently only available for public repositories.

To get started, head over to the "GitHub Sync" settings and connect your repository.

Today we shipped our widget and also added a sitemap to all public changelogs.

Widget

Use our widget to show the latest changelog entries directly within a website. No need for users to leave your website or platform. Implementation should not take longer than 2 minutes and is really straightforward.

To see a demo and setup instructions, log in to your account and head over to the "Widget" settings.

Sitemap

We also added a sitemap.xml to all changelogs. You can, for example, submit this sitemap to the Google Search Console or use it anyway you need. Just append /sitemap.xml at the end of your workspace url, e.g. example.com/sitemap.xml