Here's version 0.20.3 of GoToSocial; it's a bugfix release!
If you're updating to this version from v0.20.0, v0.20.1, or v0.20.2, it's a very easy update with no db migrations.
If you're updating to this version from a version before v0.20.0, please follow the update instructions from v0.20.0, but replace 0.20.0 with 0.20.3 throughout. Be aware that the update to 0.20.x contains some potentially very long migrations. Please do read the notes carefully!
If you are currently on a snapshot / nightly build, stay on the snapshot / nightly build, as it's already ahead of this release.
Release highlights
Bugfixes and updates to robots.txt.
Migration notes
Upgrading
To upgrade to v0.20.3 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.dbfile, 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.dbfile, 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.3ordocker pull docker.io/superseriousbusiness/gotosocial:latestif 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
No changes since previous release.
Database Migrations
No migrations since previous release.
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.3
|
| Linux | Armv8/ARM64 (64-bit) | 🟢 Full | linux_arm64.tar.gz | docker.io/superseriousbusiness/gotosocial:0.20.3
|
| 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
Bug fixes
- 87b026d54c6f8571305dc41ac784503e40cc73f5: [bugfix] Check that token is defined before logging the user out (#4632) (@prettysunflower)
- c00f640f3dcf752c287e8c89c29831501cfc2a1a: [bugfix] Mark targets of pre-approved polite interaction requests as no longer pending approval (#4647) (@kipvandenbos)
- dff7845ac2a41b2acd091a1f4001fd6ea5feeee4: [bugfix] Check follow req as well as follow when building relationship model (#4605) (@kipvandenbos)
- 5ca7f0b20785bac1e17e783b2505260283ef5385: [bugfix] Remove follow (req) notifications on Follow Undo (#4604) (@kipvandenbos)
- 2e697a7f989ef95c9be544928a61d4650b4ae337: [bugfix] don't apply visibility / status filtering when requesting your own account statuses (#4597) (@gruf)
- a4aad7af1a48cc1f28420b64a44d82e023062a0e: [bugfix] potential race condition on status unboost (#4596) (@gruf)
- 61ffbba4d952bbd2df1a018c40d91da1dc62c8e1: [bugfix] Return unboosted status with reblogged=false (#4593) (@kipvandenbos)
Chores & version bumps
- ef16f6e96d4df3bdc88e3a071a5779bb23db5d86: [chore] Update robots.txt md5 hashes for etags (#4623) (@kipvandenbos)
- a6d897b33a58ebfed8156f3af0bed717d50dbdff: [chore] Update robots.txt with latest list of "ai" bullshit user-agents (#4622) (@kipvandenbos)