superseriousbusiness/gotosocial v0.21.1

v0.21.1 Sacrilegiouser Sloth

on Codeberg

Here's version 0.21.1 of GoToSocial.

If you're updating to this version from v0.21.0, it's a very easy update with no db migrations.

If you're updating to this version from a version before v0.21.0, please follow the update instructions from v0.21.0, but replace 0.21.0 with 0.21.1 throughout. Be aware that the update to 0.21.x contains some database migrations. Please do read the notes carefully!

Release highlights

Bugfixes! Check the changelog at the bottom for details.

Migration notes

Upgrading

To upgrade to v0.21.1 from a previous release:

Binary/tar

1. Stop GoToSocial.
2. Back up your database! If you're running on SQLite, this is as simple as copying your sqlite.db file, eg., cp sqlite.db sqlite.db.backup. On Postgres you can do this with pg_dump.
3. Download and untar the new release, including the web assets and html templates, not just the binary.
4. Edit your config.yaml file if necessary (see below).
5. Start GoToSocial.
6. Wait patiently for any migrations to run, do not interrupt migrations or you could leave your db in a broken state and will have to restore from backup!
7. Enjoy your updated instance.

Docker

1. Stop GoToSocial.
2. Back up your database! If you're running on SQLite, this is as simple as copying your sqlite.db file, eg., cp sqlite.db sqlite.db.backup. On Postgres you can do this with pg_dump.
3. Pull the new docker container with docker pull docker.io/superseriousbusiness/gotosocial:0.21.1 or docker pull docker.io/superseriousbusiness/gotosocial:latest if this is a stable release and not a release candidate.
4. Edit your config.yaml file or environment variables if necessary (see below).
5. Start GoToSocial.
6. Wait patiently for any migrations to run, do not interrupt migrations or you could leave your db in a broken state and will have to restore from backup!
7. Enjoy your updated instance.

config.yaml

No changes since v0.21.x.

Database Migrations

No migrations since v0.21.x.

Which release archive/container should I use?

GoToSocial releases binary builds for 64-bit Linux, FreeBSD, and NetBSD operating systems. We also release Docker builds for 64-bit Linux.

nowasm

For your convenience, we also provide UNSUPPORTED, EXPERIMENTAL BUILDS, created using the nowasm tag, in the downloads list below. There is no Docker build for nowasm.

GoToSocial releases built with nowasm use the Go-native, modernc version of SQLite instead of the WASM one, and will use on-system ffmpeg and ffprobe binaries for media processing.

Using a nowasm build is currently the only way to run GoToSocial on a 32-bit system.

For more information on running a nowasm build, see the nowasm documentation page.

Changelog

Bug fixes

• 55764cea3e00eca5141633d06493812e41323bf7: [bugfix] Check replyAuthorization prop on statuses, fall back to deprecated approvedBy (#4732) (@kipvandenbos)
• 769f1f6cee4d42e01ae8d5c20c71eea591b582de: [bugfix] catch empty media attachment URLs and set appropriate error text so they get replaced with placeholder text (#4723) (@gruf)
• 0cc82b8da60cd96d594fcd1ecd04cdcc06ce68f6: [bugfix] ensure domain limit status filters get serialized the same as regular status filters (#4722) (@gruf)
• b5fd5860dd35933979389cc3ee3c442453611896: [bugfix] do not crash on null media.meta on reports page (#4721) (@mkljczk)
• 387b3d2769a106abdef4cb25a36ab6760dc49102: [bugfix] Fix missing prometheus go runtime metrics (#4718) (@kipvandenbos)

Chores & version bumps

• 4931fe744c62d2726b20e1a0025b9e99bb13a128: [chore] updated dependencies (#4719) (@gruf)
• b0e32160d8c4dcfc1b860fe10bd44d09cc2fb271: [chore] Updating linter in CI/CD to v2.9.0 (#4714) (@foxbite)