TECH Signal 401
Apprise 1.13 released as last 1.x version before breaking 2.0 changes
Apprise 1.13 adds new notification services, encryption, and rich messages while marking the end of the 1.x line ahead of incompatible 2.x updates
Engineers using Apprise for notifications must pin dependencies to avoid automatic upgrades to 2.x, which will introduce breaking changes. The 1.x branch will still receive security fixes for now, but migration planning should begin soon.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Apprise 1.13 introduces support for three new notification services and retires NotificationApi
Telegram rich messages and Bark AES-GCM encryption are now available, with fixes for Matrix, email, and webhook issues
The 1.x series ends with this release; 2.x will bring breaking changes requiring dependency constraints
THE READ
What the cluster adds up to.
Apprise 1.13 is the final feature update in the 1.x series, signaling a shift toward a 2.x branch with incompatible changes. Developers integrating Apprise into applications must constrain dependencies to versions below 2.0 to prevent unintended upgrades. While security fixes will continue for 1.x, the transition to 2.x will eventually require code adjustments, making early planning necessary for production systems.
The release adds support for Pinglet, Trigv, and Pingram, replacing the now-retired NotificationApi service. Encryption improvements for Bark and rich message support for Telegram expand functionality, while fixes for Matrix, email attachments, and webhooks address reliability issues. These changes improve flexibility but may require testing for existing integrations, particularly where new services or encryption methods are adopted.
Maintenance updates in 1.13 include better CLI documentation, proxy details in the man page, and an Italian translation. While these are minor, they reflect ongoing polish for the 1.x branch. However, the focus on 2.x development suggests future feature work will prioritize the new branch, leaving 1.x in a maintenance-only state. Teams should evaluate whether to adopt 1.13’s new features now or wait for 2.x’s stability.
The breaking changes in 2.x are not yet detailed, but the warning to pin dependencies implies significant API or behavior shifts. Engineers should monitor the project’s roadmap and test early 2.x releases to assess migration effort. For now, the 1.x branch remains viable for security updates, but long-term support will depend on 2.x’s adoption and stability.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗