Mastodon @Mastodon@mastodon.social

This is a backport release, so if you are already using the latest code from the master branch, you already have all these fixes.

⚠️ #Mastodon v3.2.1 is out with some long overdue bug fixes:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.1

Blog post! Mastodon 3.2:

https://blog.joinmastodon.org/2020/08/mastodon-3.2/

Share with your friends!

🎉 It is time! #Mastodon 3.2.0 is here! What's in it? Have a look:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0

🎉 #Mastodon 3.2.0rc2 is out:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0rc2

Closing in on stable release!

🎉 The first release candidate of #Mastodon 3.2.0 is out:

https://github.com/tootsuite/mastodon/releases/tag/v3.2.0rc1

⚠️ #Mastodon v3.1.5 is out with a few important security fixes:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.5

There will be a small v3.1.5 release with important security fixes soon. Please be prepared to upgrade swiftly!

v3.2.0 with cool new features will come after that!

⚠️ An issue has been reported with the `tootctl upgrade storage-schema` command in relation to DigitalOcean Spaces. Avoid executing that for now if you're using Spaces.

Also, a warning has been added to the release notes: You don't need to run that command at all. It would incur data transfer costs to do so as it moves files around.

🎉 #Mastodon v3.1.4 is out:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.4

This release includes many bugfixes, ability to remove Keybase proofs from your account, support for new unicode emoji, improvements around delivery to dead servers, and new options for browsing public timelines!

@Tenacious This message is for people who run Mastodon servers. As a user, you don't have to do anything.

⚠️ #Mastodon v3.1.2 is out with an important security fix:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.2

Likewise, v3.0.2 and v2.9.4 have been released to port this fix to older versions.

@saper @matt Based on what was said I think this is simply a matter of database migrations not having been run.

@matt Yes, you can go straight from one version to another skipping the ones in between.

Most of the upgrade instructions overlap. Rarely, there are instructions that are special to some release. It's absolutely fine to run them on the latest release, just have to run them as well.

@matt Here is the release page for v3.1.0:

https://github.com/tootsuite/mastodon/releases/tag/v3.1.0

v3.1.0 was immediately replaced by v3.1.1 so all these notes are for v3.1.1 as well. Scroll down to "Upgrade instructions".

@matt People often miss this sentence: "The release page contains a changelog, and below it, upgrade instructions"

You need to follow the instructions on the particular release's page. Have you done that? Or have you only executed assets:precompile which is the example given below?

@matt Do you mean this guide?

https://docs.joinmastodon.org/admin/upgrading/