Notifuse releases, newest first. Before you upgrade, read the notes of every release between your version and the new one, then follow Upgrade to a new release.
44.0
November 19, 2026
With 194 changelog entries, this is the largest Notifuse release so far. The console is rebuilt on a new design, every email gets a plain-text version and a web version, and the email editor writes MJML 5. Notifuse now compiles emails with safe-mjml 1.1 and renders Liquid with liquidgo 5.14.6, which behaves like Shopify Liquid in many more cases.
This is also a security release: Liquid values in the HTML of emails are now HTML-escaped, so data from a public form can no longer add markup or links to an email.
- The console has a denser look, a sidebar that folds to icons and a new dashboard, and contacts, lists and segments share one page.
- Every email includes a plain-text version, and broadcast and automation emails can link to their web version with
{{ view_in_browser_url }}. - Automations can start when a contact clicks a link, and their emails can use the event that started the journey as
{{ trigger_event }}. - New templates start from a gallery of 15 ready-made emails, and blocks of the visual editor can be shown only to some recipients.
- A scheduled broadcast can go back to draft, and each variation can choose its own sender.
compose.yamlinstalls Notifuse from the published image and moves to PostgreSQL 18. The workspace list says when a new version is out, unlessCHECK_FOR_UPDATES=false.
Warning
Before you upgrade:
- Notifuse no longer starts on PostgreSQL older than 17. Upgrade the database server first, as Upgrading PostgreSQL explains.
- With
compose.yaml, the nextdocker compose up -dupgrades PostgreSQL 17 to 18 after copying its data to thepostgres-upgrade-backupvolume. Keep free disk space for the data plus 10%. Every variable of.envnow reaches Notifuse, so remove stale settings first. - The upgrade rebuilds indexes on the message history, and sending and tracking wait until it ends, about a second per 2 million messages when the table fits in memory. Plan it outside a large send.
- Data meant to be HTML needs the new
rawfilter ({{ global_feed.html | raw }}), and{{ bio | newline_to_br }}becomes{{ bio | escape | newline_to_br }}. - An email whose Liquid fails, for example by comparing a text with a number or calling a filter without a required argument, is no longer sent. The preview and the test send show the error.
- If you set
email.textthrough the API, it is now sent as the email’s text version. - On a blog’s custom domain, rename any category whose slug is
v: the/v/path now belongs to web versions. email.testProvideris limited to workspace owners. API keys and members now get 403.- Segment memberships change at the upgrade. Automations and webhooks that react to a contact joining or leaving a segment receive these changes at once.
Release post · Full 44.0 entry
43.0
November 7, 2026
Contacts choose open and click tracking separately, workspaces decide what happens without a recorded choice, and email integrations slow down when a provider says emails arrive too fast.
- Contacts can agree to or refuse open tracking and click tracking, each on its own.
- Workspace settings turn open and click tracking on separately, with a default for contacts without a recorded choice.
- Broadcasts and transactional notifications can be sent without tracking, keeping their UTM parameters.
- Automations carry contacts through more than ten steps in a row without a delay.
Warning
Before you upgrade:
- Check that Exclude unsubscribed recipients is on for your regular campaigns, including those created through the API without
exclude_unsubscribedbefore 42.0. A broadcast with it off no longer carries theList-Unsubscribeheader. - Contact webhook payloads gain four tracking consent fields. Make sure a receiver that validates payloads accepts them.
42.2
November 5, 2026
Safer tracked links, and workspaces whose creation stopped partway can be created again. This is a security release: tracked links no longer send visitors to a site the email did not contain without asking them first, and requests naming a workspace that does not exist no longer open database connections.
- Tracked links ask the visitor to confirm before opening a site Notifuse cannot verify the email contained.
- A workspace whose creation stopped partway can be created again under the same ID.
- An owner without a licence for granular permissions can put a member back on full access.
Warning
Before you upgrade: if you can, upgrade while no broadcast is paused or still sending. Emails queued before the upgrade go out with unsigned links, and their links to other sites show a confirmation page.
42.1
October 28, 2026
A security update for single sign-on, with a fix for fonts declared in email templates and stricter SMTP credential checks. Single sign-on now uses go-jose 4.1.6, which fixes a denial of service through a crafted RSA key in the identity provider’s signing keys (GHSA-mgcc-cww5-fp2q).
- Fixes a denial of service in single sign-on.
- A font declared with
mj-fontnow replaces Google’s stylesheet for the same font. - SMTP settings require a password with a username, and a username with a password.
42.0
October 23, 2026
A security release that also hardens SECRET_KEY handling and fixes how lists, unsubscribes and broadcasts behave. It closes several vulnerabilities: webhooks could reach private and internal addresses, provider webhooks acted on emails Notifuse had not sent, the email editor ran scripts from template content, and dependencies and the Go runtime had known advisories.
- Webhooks refuse private, loopback and reserved addresses unless
WEBHOOK_DELIVERY_ALLOW_PRIVATE_HOSTSis set. SECRET_KEYcan list several keys, so you can replace it.- Broadcasts follow each email integration’s rate limit and reach large lists faster.
- A contact removed from a list is treated as off the list everywhere.
Warning
Before you upgrade:
- If your webhooks reach a service on your own network (n8n or another container on the same Docker network, an internal API), set
WEBHOOK_DELIVERY_ALLOW_PRIVATE_HOSTS=truebefore you upgrade. Otherwise those webhooks stop delivering. - If a relay of yours posts events for an SMTP integration to
/webhooks/email, set each event’smessage_idto the email’sX-Message-IDheader and itsrecipientto the address the email was sent to. - If your
SECRET_KEYis the formercompose.yamldefault, theenv.exampleplaceholder or shorter than 32 bytes, Notifuse no longer starts with it. In the same step as the upgrade, generate a new key and setSECRET_KEY=<new key>,<current key>, as Replacing the secret key explains. - If your
SECRET_KEYcontains a comma, write each of its commas twice in the same step as the upgrade. - Building from source now requires Go 1.26.10 or later.
Earlier releases
The full history, back to version 3.1, is in CHANGELOG.md on GitHub.
