Skip to content

v4.1.11
Compare
Choose a tag to compare
@ClearlyClaire ClearlyClaire released this 04 Dec 14:52
· 51 commits to stable-4.1 since this release
v4.1.11
363bedd

Mastodon

This is a bugfix release for the 4.1.x branch. Please consider updating to the 4.2.x branch if you haven't done so yet.

Changelog

Changed

  • Change GIF max matrix size error to explicitly mention GIF files (ClearlyClaire)
  • Change Follow activities delivery to bypass availability check (ShadowJonathan)
  • Change Content-Security-Policy to be tighter on media paths (ClearlyClaire)

Fixed

  • Fix incoming status creation date not being restricted to standard ISO8601 (ClearlyClaire, ClearlyClaire)
  • Fix posts from force-sensitized accounts being able to trend (ClearlyClaire)
  • Fix processing LDSigned activities from actors with unknown public keys (ClearlyClaire)
  • Fix error and incorrect URLs in /api/v1/accounts/:id/featured_tags for remote accounts (ClearlyClaire)
  • Fix report processing notice not mentioning the report number when performing a custom action (ClearlyClaire)
  • Fix some link anchors being recognized as hashtags (ClearlyClaire, ClearlyClaire)

Upgrade notes

To get the code for v4.1.11, use git fetch && git checkout v4.1.11.

As always, make sure you have backups of the database before performing any upgrades. If you are using docker-compose, this is how a backup command might look: docker exec mastodon_db_1 pg_dump -Fc -U postgres postgres > name_of_the_backup.dump

Dependencies

External dependencies have not changed compared to v4.1.7, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

  • Ruby: 2.7 to 3.0
  • PostgreSQL: 9.5 or newer
  • Elasticsearch (optional, for full-text search): 7.x
  • Redis: 4 or newer
  • Node: >= 14, < 18
  • ImageMagick: 6.9.7-7 or newer

If your uploaded images are broken after the upgrade, it means your installed ImageMagick version is older than the new minimum version (6.9.7-7), for example if you are running Ubuntu 18.04. If this happens, you can find more information and ways to fix it on this page.

Update steps

The following instructions are for updating from 4.1.10.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

  1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

  1. Restart all Mastodon processes
Assets 2