← Back to all sparks
A

Apprise

COMMS
Velocity6.3

Unified notification delivery across dozens of messaging services

The final v1.x release slipped by one patch, but the v2 deadline stands.

notificationsmajor-versiondeprecationroutingcommunitypython
Current state
Apprise is a Python notification library that fans a single call out to more than 150 services. Weighted tagging in v1.11 turned that fan-out into ordered delivery with fallback, and the releases since have been service accretion and bug clearance. v1.13.0 was announced as the last of the v1.x line; v1.13.1 has now shipped anyway, adding Signalgrid and Lauther support and fixing a memory-backed attachment failure, with the maintainer repeating the end-of-line notice and adding that he means it this time.
Where it's heading
The v1 line is being closed out in patches rather than stopped cleanly, which is the normal shape of a maintainer-led project absorbing community pull requests faster than it can cut a major version. The ask to downstream projects has not changed — pin to >=1.0.0,<2.0.0 — and v1.x is stated to keep security support for a year or two after v2 lands. What v2 actually breaks is still not described in any of these entries.
Prediction
The next release is likely another v1.x patch of the same shape — community service plugins plus attachment and protocol fixes — unless a v2 alpha appears first. Nothing in these entries indicates which.

Recent moves

  1. 16d ago

    Final v1.x patch: attachment fix and two more services

    A patch release the maintainer describes as small, and it is: Signalgrid and Lauther join the service catalog, Pingram API keys in JWT format now parse, and the stated reason for cutting it at all is a Gentoo-specific failure in memory-backed attachment handling. Python 3.13 is now permitted. The repeated notice that v1.x ends here carries no new information beyond v1.13.0 — it is the same deadline, restated after one more patch shipped past it.

    View source ↗
  2. 26d ago

    Last release of the v1.x line — pin before v2 breaks

    ⚡ SPARK

    Presented as a routine maintenance drop — three new services and a long bug list — but the notice buried in it is the real content: v1.13.0 is the final v1.x release, and every downstream project is asked to pin below 2.0.0 now. The community out-committed the maintainer on this one, which the release notes call a first.

    View source ↗
  3. 2mo ago

    Past 150 services, with HTML-to-Markdown conversion built in

    The monthly bundle that pushes the catalog past 150 services, adding Stackfield, PushWard, MailerSend, Notifyer, Kook and others in one pass. Built-in HTML to Markdown conversion is the more durable change — it removes a preprocessing step for anyone feeding rich content into services that only accept plain formats.

    View source ↗
  4. 3mo ago

    Tags gain weights, turning notification fan-out into failover

    ⚡ SPARK

    This is where Apprise stops being purely a fan-out layer: tags can carry a weight, and delivery walks the priority levels in order, only falling through when a level fails. Everything the library did before still works unchanged, but routing is now something it decides rather than something the caller pre-computes.

    View source ↗
  5. 5mo ago

    XMPP multi-user chat and the groundwork for the URL Builder

    Described in its own notes as a mini release, it adds XMPP multi-user chat support and fixes a send/disconnect race condition in the same protocol. The details() JSON response and repo cleanup are explicitly staging for the URL Builder — an example of how much recent work serves the documentation site rather than the library itself.

    View source ↗
  6. 6mo ago

    IRC support arrives and XMPP returns via Slixmpp

    A heavy service release: IRC with ZNC bouncer support, Viber Bot, Fluxer, a jellyfin alias for Emby, and XMPP restored on Slixmpp after a period without it. Slack OAuth bot rotation support is the operational note here — token rotation is what separates a demo integration from one that survives in production.

    View source ↗