1.12.0

This release adds support for Lemmy 0.19.

Note: Due to breaking changes, this Lemmy version requires a bit more complex of a release timeline.

One of the next few releases of Voyager will be v2. Voyager v2 will break support for lemmy v0.18 for progressive webapp clients! This is due to CORS limitations where web clients cannot set a custom Cookie header for backward compatibility, and the new v0.19 lemmy-js-client removes authentication via the auth url param.

Actions required

Native app users

No action required! Voyager will continue to support Lemmy v0.18 for the foreseeable future, while adding support for new v0.19 features over time.

PWA (https://vger.app) users

Voyager running on https://vger.app will continue to support Lemmy v0.18 until v0.19 has been out for a while and all large instances have upgraded. This will be accomplished by pinning https://vger.app to Voyager v1. After some time, https://vger.app will drop support for v0.18 by upgrading to Voyager v2. Dropping support for Lemmy v0.18 will allow supporting new v0.19 features.

Voyager self-hosters

v2 of Voyager will be released soon. Voyager v2 will break support for Lemmy v0.18 for PWA clients, and Voyager v2 may be released before Lemmy v0.19 is released. If you have Voyager auto-updating via watchtower or some other means, I recommend to disable it until your instance updates to Lemmy v0.19.

What's Changed

• Revert "Added one additional text face (#651)" by @dandroid126 in #712
• Add lemmy v0.19 authentication support by @aeharding in #750

Full Changelog: 1.11.4...1.12.0