We're pleased to be publishing the release candidate for v2.15.0 (the official release should follow within two weeks or so). This release adds support for mobile push notifications, via the draft/webpush specification. More information on this is available in the manual and user guide. This feature is still considered to be in an experimental state; default.yaml ships with it disabled, and its configuration may have backwards-incompatible changes in the future.
This release includes changes to the config file format, all of which are fully backwards-compatible and do not require updating the file before upgrading.
This release includes a database change. If you have datastore.autoupgrade set to true in your configuration, it will be automatically applied when you restart Ergo. Otherwise, you can update the database manually by running ergo upgradedb (see the manual for complete instructions).
Many thanks to @delthas, @donatj, donio, @emersion, and @eskimo for contributing patches and helping test.
Config changes
- Added
webpushblock to the config file to configure push notifications. Seedefault.yamlfor an example. Note that at this time,default.yamlships with support for push notifications disabled; operators can enable them by settingwebpush.enabled: true. In the absence of such a block, push notifications are disabled. - We recommend the addition of
"WEBPUSH": 1tofakelag.command-budgets, to speed up mobile reattach when web push is enabled. Seedefault.yamlfor an example.
Added
- Added support for the draft/webpush specification (#2205, thanks @emersion, @eskimo!)
- Added support for the draft/extended-isupport specification (#2184, thanks @emersion!)
UBAN ADDnow acceptsREQUIRE-SASLwith NUH masks, i.e. k-lines (#2198, #2199)- Ergo now publishes the
SAFELISTISUPPORT parameter (#2196, thanks @delthas!)
Fixed
- Fixed incorrect parameters when pushing
005(ISUPPORT) updates to clients on rehash (#2184)