We are running the latest release candidate for Lemmy, version 0.19.0-rc.1. This release candidate includes many changes.
Every release comes with its own challenges; however, it resolves previous ones. We hope this release will resolve a longstanding issue with sync not working, causing a lot of manual work from the admins to keep things in sync.
Please let us know if you experience any weird behavior.
Some known issues so far are:
- HTML entities characters in posts bodies (Changing & to &)
- The
spoilertag crashes the site if used in the sidebar - Mobile apps are borked again
Update 10/25/2023
- We are now running release candidate 3.
We've tried rolling back multiple times in a couple of different ways. They all end up failing. From what we have seen through it all, Lemmy doesn't support downgrading/rolling back
Thanks for responding. It’s disappointing that not a single third party app seems to work with 0.19RC.
Can nothing be done ?
Lemmy changed their API contract with mobile apps without warning or API versioning. They changed how requests are authenticated, so it's not the most simple of fixes. Ideally, this change would be a new API version not to break previous integrations; however, that's not how it was done.
We continue to update because issues are resolved with every release; however, new ones appear. We traded some sync issues for API issues.
Sorry for the inconvenience.
I took this up with Lemmy devs and was pointed here: https://lemmy.ml/post/5711722 Where 0.19 was described and admins warned not to use it in production and to have backups due to it being unstable.
Yes, that came out later after we upgraded. We ran the
latesttag, which wasn't stable (typically, that tag is), and included some 0.19 code. So, we were stuck moving forward. Lemmy doesn't roll back. So we either had to lose a week of content, users, etc, or keep moving forward with the latest version. The good news is some bugs are fixed.Something could be done. We could fork 0.19 and restore the previous authentication methods. I don't have the time available to do that. If someone does it we'd be happy to run it.