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

Note Detail

Reply to @gotosocial@gts.superseriousbusiness.org
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
---Reply---
GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-19 22:11:06)
Third release candidate for v0.22.0 of #GoToSocial!

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

Compared to rc2:

Unfollow relay actor if no connections exist targeting that actor (allows retrying establishing relay connection by removing all connections to an actor + creating a new one).
Fix erroneus use of RelayConnectionCreateRequest when updating a relay push.
Don't error on db.ErrNoEntries in OnMediaDereference callback.
Disable outgoing http2 requests until superseriousbusiness/httpsig is updated, as our signatures were getting messed up by http2 transport.
Only mark status as edited for streaming hooks if edited_at column has changed.
Remove admin check on user-level relay push matchers.
Set statuses-cleanup-remote-older-than to "0s", skip scheduling if 0.
Fingers crossed this is the last one :)

Thanks for all the help finding bugs, everyone <3

---Replies---

GoToSocial@gotosocial@gts.superseriousbusiness.org (2026-06-25 17:20:39)
Hello hello hello, what's all this then? The fourth #GoToSocial v0.22.0 release candidate?

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

⚠️ We strongly urge everyone currently using v0.22.x release candidates from rc3 or lower to update to this release, as it contains some important bugfixes related to exif data stripping and a security fix for a vulnerability whereby malformed AP messages can cause mischief. We will make a more detailed post about this vulnerability next week, to give people time to update. ⚠️

Compared to rc3:

Postgres home timeline query performance improvements.
Bugfixes for timelining and streaming relayed statuses (statuses from subscribed relays actually appear in the federated timeline now 🤦‍♀️).
Bug fixes related to exif stripping and malformed AP messages.
Dependency updates.
Thanks! Have a nice day! Stay cool and crisp!