This is a rerelease of the 4.2.2 bugfix release, as a dependency used by Mastodon 4.2.0 through 4.2.2 has been removed. If you are installing from a version earlier than 4.2.0, please check the 4.2.0 release notes as they contain important information on how to update.

Changelog (v4.2.3)

Fixed

• Fix dependency on json-canonicalization version that has been made unavailable since last release

Changelog (v4.2.2)

Changed

• Change dismissed banners to be stored server-side (ClearlyClaire)
• Change GIF max matrix size error to explicitly mention GIF files (ClearlyClaire)
• Change Follow activities delivery to bypass availability check (ShadowJonathan)
• Change single-column navigation notice to be displayed outside of the logo container (renchap, renchap)
• Change Content-Security-Policy to be tighter on media paths (ClearlyClaire)
• Change post language code to include country code when relevant (gunchleoc, ClearlyClaire)

Fixed

• Fix upper border radius of onboarding columns (ClearlyClaire)
• Fix incoming status creation date not being restricted to standard ISO8601 (ClearlyClaire, ClearlyClaire)
• Fix some posts from threads received out-of-order sometimes not being inserted into timelines (ClearlyClaire)
• Fix posts from force-sensitized accounts being able to trend (ClearlyClaire)
• Fix error when trying to delete already-deleted file with OpenStack Swift (ClearlyClaire)
• Fix batch attachment deletion when using OpenStack Swift (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 handling of inLanguage attribute in preview card processing (ClearlyClaire)
• Fix own posts being removed from home timeline when unfollowing a used hashtag (kmycode)
• Fix some link anchors being recognized as hashtags (ClearlyClaire, ClearlyClaire)
• Fix format-dependent redirects being cached regardless of requested format (ClearlyClaire)

Upgrade notes

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

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 since v4.2.0, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0 to 3.2
• PostgreSQL: 10 or newer
• Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
• LibreTranslate (optional, for translations): 1.3.3 or newer
• Redis: 4 or newer
• Node: 16 or newer
• 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.2.1.

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
2. Precompile the assets: RAILS_ENV=production bundle exec rails assets:precompile
3. Restart all Mastodon processes

Using Docker:

1. Restart all Mastodon processes