this post was submitted on 20 Jun 2023
68 points (100.0% liked)

Announcements

23297 readers
29 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago
MODERATORS
dessalines@lemmy.ml
nutomic@lemmy.ml
68
Lemmy 0.18 is ready for testing (lemmy.ml)
submitted 1 year ago by nutomic@lemmy.ml to c/announcements@lemmy.ml
41 comments fedilink hide all child comments
 

The new major version of Lemmy is now ready, and we need your help with testing. Most importantly it uses HTTP for API requests now, which is much more efficient than websocket. Additionally Two-factor-auth is supported. There are also countless other improvements and bug fixes.

You can register on any of the following servers to start testing, no approval required. You can post to your hearts content to find out if anything is broken. The test instances only federate with each other to avoid affecting production instances with spam.

If you encounter any bugs that aren't present in 0.17, open an issue and mention in the title that it happened with a release candicate version. Over the next days we will publish new RC versions to fix bugs that will invariably pop up.

Instance admins can try the new version by using Docker images dessalines/lemmy-ui:0.18.0-rc.2 and dessalines/lemmy:0.18.0-rc.1. Make sure that working backups are in place. For production instances its better to wait at least some days for the major issues to be fixed.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] lodion@aussie.zone 2 points 1 year ago* (last edited 1 year ago) (2 children)

Posted this on Martrix... but receiving this error on all three instances on clicking the "Sign Up" button after entering my details:


edit: Also DS seems to require admin approval for new signups.

[โ€“] lodion@aussie.zone 1 points 1 year ago

FWIW I tried an hour later and it worked. Not sure if something was fixed in the back end.

load more comments (1 replies)