Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @gotosocial@gts.superseriousbusiness.org
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 23:50:21)
Alright due to the bug in #GoToSocial v0.22.0-rc1 specifically for SQLite users which causes migrations to fail, we recommend SQLite users wait for v0.22.0-rc2, which we'll be releasing shortly (hopefully within a couple hours). (Postgres users are unaffected.)

Thanks for your patience! And thanks for the bug reporters for notifying us about it! <3
---Reply---
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-16 23:51:25)
In case you're interested, it was a single-character bugfix in our go-sqlite3 dependency: https://github.com/ncruces/go-sqlite3/issues/401#issuecomment-4719291828

Big thanks to Nuno for responding so promptly!!

---Replies---

GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-17 00:39:53)
As promised here's the second release candidate for #GoToSocial v0.22.0:

https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0-rc2

Compared to the first release candidate:

Fixed a bug that was causing migrations on SQLite to fail with an erroneous out of memory panic.
Fixed a bug with streaming + assets endpoints on split-domain deployments.
Enjoy! Have fun! Post gay nerd shit! <3