superseriousbusiness/gotosocial v0.20.1 on Codeberg

Here's version 0.20.1 of GoToSocial.

Please read the migration notes carefully for instructions on how to upgrade to this version.

Release highlights

Pee pee
Poo poo
Wee wee

Migration notes

Upgrading

To upgrade to v0.20.1 from a previous release:

Binary/tar

Stop GoToSocial.
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.
Download and untar the new release, including the web assets and html templates, not just the binary.
Edit your config.yaml file if necessary (see below).
Start GoToSocial.
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!
Enjoy your updated instance.

Docker

Stop GoToSocial.
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.
Pull the new docker container with docker pull docker.io/superseriousbusiness/gotosocial:0.20.1 or docker pull docker.io/superseriousbusiness/gotosocial:latest if this is a stable release and not a release candidate.
Edit your config.yaml file or environment variables if necessary (see below).
Start GoToSocial.
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!
Enjoy your updated instance.

config.yaml

The configuration file has changed since the previous release.

Changed pee pee to poo poo.
Changed wee wee to more wee wee.

You can see a diff of the config file here: https://codeberg.org/superseriousbusiness/gotosocial/compare/v0.20.0...v0.20.1#diff-c071e03510b2c57e193a44503fd9528a785f0f411497cc75841a9f8d0b1ac622

Database Migrations

⚠️⚠️⚠️

This release may contain database migrations which will run the first time you start up this new version.

Be sure not to interrupt this migration process.

This will take anywhere between a couple seconds and ten minutes or more (on slower hardware).

Please be patient!

⚠️⚠️⚠️

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.

OS	Architecture	Support level	Binary archive	Docker
Linux	x86-64/AMD64 (64-bit)	🟢 Full	linux_amd64.tar.gz	`docker.io/superseriousbusiness/gotosocial:0.20.1`
Linux	Armv8/ARM64 (64-bit)	🟢 Full	linux_arm64.tar.gz	`docker.io/superseriousbusiness/gotosocial:0.20.1`
FreeBSD	x86-64/AMD64 (64-bit)	🟢 Full	freebsd_amd64.tar.gz	Not provided
FreeBSD	Armv8/ARM64 (64-bit)	🟢 Full	freebsd_arm64.tar.gz	Not provided
NetBSD	x86-64/AMD64 (64-bit)	🟢 Full	netbsd_amd64.tar.gz	Not provided
NetBSD	Armv8/ARM64 (64-bit)	🟢 Full	netbsd_arm64.tar.gz	Not provided

`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

Features and performance

2bdff66f0a12a16684e5d25bcace551446ec1c78: [performance] cache account IDs in home timeline query not in exclusive lists (#4502) (@gruf)
c99b89f780f9d561ac0fbc2acf61291006396071: [feature] granular admin scopes for custom emojis (#4489) (@vyr)

Bug fixes

717fd7604aa7ae49acb51b9e7bd6b2cce046f85b: [bugfix] Fix HTTP return code for Likes of remote statuses (#4504) (@kipvandenbos)
c9208ae56c7a8b4846711674021de2c359c57755: [bugfix] rss feed validation (#4499) (@gruf)
eaaf2d75bdde5f522ed9479cc1c2f99e92fdfe9c: [bugfix] Fix "client IP could not be parsed" error msg (#4497) (@kipvandenbos)
3a5119b5ff2c8f6ecb02d4054002b3845ca05e9c: [bugfix] repeated posts on timeline endpoints (#4494) (@gruf)

Chores & version bumps

ee4294af006cbf10c3061cf23ee16bb42b91ec3f: [chore] Better handling of Gone accounts during PostInbox (return 202 Accepted instead of 401 Unauthorized) (#4506) (@kipvandenbos)
6fee55dcff976f3eeae5879fe91d2f27780d0da4: [chore] Rationalize HTTP return codes for fedi endpoints, other tidying up (#4503) (@kipvandenbos)
db8e26b60e1d3a81580d21f90ea46d63e3c50fb8: [chore/performance] Use CTE for list select statuses query (#4501) (@kipvandenbos)
ea7eeada77a52fd58a9e1a949a39eccc7bce955a: [chore] update dependencies (#4495) (@gruf)

Documentation

c9fcf3f11cac21cc326fd20a34cae3d629aad0c3: [docs] Document setting OTEL_EXPORTER_PROMETHEUS_HOST for Docker (#4498) (@kipvandenbos)