v4.2.1

This is a bugfix release for the 4.2.0 version, if you're installing from an earlier version, please check the 4.2.0 release notes as they contain important information on how to update.

⚠️ We recently released important security updates.

If you don't want or can't update to 4.2.x yet, the security updates are also available for the 4.1.x branch, the 4.0.x branch and the 3.5.x branch.

Changelog

Added

• Add redirection on /deck URLs for logged-out users (ClearlyClaire)
• Add support for v4.2.0 migrations to tootctl maintenance fix-duplicates (ClearlyClaire)

Changed

• Change some worker lock TTLs to be shorter-lived (ClearlyClaire)
• Change user archive export allowed period from 7 days to 6 days (suddjian)

Fixed

• Fix clicking on already-opened thread post scrolling to the top of the thread (ClearlyClaire, ClearlyClaire)
• Fix some remote posts getting truncated (ClearlyClaire)
• Fix some cases of infinite scroll code trying to fetch inaccessible posts in a loop (ClearlyClaire)
• Fix Vary headers not being set on some redirects (ClearlyClaire)
• Fix mentions being matched in some URL query strings (mjankowski)
• Fix unexpected linebreak in version string in the Web UI (vmstan)
• Fix double scroll bars in some columns in advanced interface (ClearlyClaire)
• Fix boosts of local users being filtered in account timelines (ClearlyClaire)
• Fix multiple instances of the trend refresh scheduler sometimes running at once (ClearlyClaire)
• Fix importer returning negative row estimates (jgillich)
• Fix incorrectly keeping outdated update notices absent from the API endpoint (ClearlyClaire)
• Fix import progress not updating on certain failures (ClearlyClaire)
• Fix websocket connections being incorrectly decremented twice on errors (ThisIsMissEm)
• Fix explore prompt appearing because of posts being received out of order (ClearlyClaire)
• Fix explore prompt sometimes showing up when the home TL is loading (ClearlyClaire)
• Fix link handling of mentions in user profiles when logged out (ClearlyClaire)
• Fix filtering audit log for entries about disabling 2FA (ClearlyClaire)
• Fix notification toasts not respecting reduce-motion (c960657)
• Fix retention dashboard not displaying correct month (vmstan)
• Fix tIME chunk not being properly removed from PNG uploads (TheEssem)
• Fix division by zero in video in bitrate computation code (ClearlyClaire)
• Fix inefficient queries in “Follows and followers” as well as several admin pages (ClearlyClaire, ClearlyClaire)
• Fix ActiveRecord using two connection pools when no replica is defined (ClearlyClaire)
• Fix the search documentation URL in system checks (renchap)

Upgrade notes

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

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.0.

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

v4.1.10

⚠️ We recently released important security updates, so if you are still using a 4.2.0 pre-release, 4.1.7 or below, 4.0.9 or below, or 3.5.13 or below, please update as soon as possible (see the release notes for v4.1.8).

Changelog

Changed

• Change some worker lock TTLs to be shorter-lived (ClearlyClaire)
• Change user archive export allowed period from 7 days to 6 days (suddjian)

Fixed

• Fix mentions being matched in some URL query strings (mjankowski)
• Fix multiple instances of the trend refresh scheduler sometimes running at once (ClearlyClaire)
• Fix importer returning negative row estimates (jgillich)
• Fix filtering audit log for entries about disabling 2FA (ClearlyClaire)
• Fix tIME chunk not being properly removed from PNG uploads (TheEssem)
• Fix inefficient queries in “Follows and followers” as well as several admin pages (ClearlyClaire, ClearlyClaire)

Upgrade notes

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

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.9.

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

v4.0.12

⚠️ The 4.0.x branch will not receive any update—including security fixes—after 2023-10-31.

⚠️ We recently released important security updates, so if you are still using a 4.2.0 pre-release, 4.1.7 or below, 4.0.9 or below, or 3.5.13 or below, please update as soon as possible (see the release notes for v4.0.10).

End of life notice

The 4.0.x branch will not receive any update after 2023-10-31.
This means that no security fix will be made available for this branch after this date, and you will need to update to a more recent version (such as the 4.1.x branch) to receive security fixes.

Changelog

Changed

• Change some worker lock TTLs to be shorter-lived (ClearlyClaire)
• Change user archive export allowed period from 7 days to 6 days (suddjian)

Fixed

• Fix mentions being matched in some URL query strings (mjankowski)
• Fix multiple instances of the trend refresh scheduler sometimes running at once (ClearlyClaire)
• Fix importer returning negative row estimates (jgillich)
• Fix filtering audit log for entries about disabling 2FA (ClearlyClaire)
• Fix tIME chunk not being properly removed from PNG uploads (TheEssem)
• Fix inefficient queries in “Follows and followers” as well as several admin pages (ClearlyClaire, ClearlyClaire)

Upgrade notes

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

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.0.9, 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.0.11.

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

v3.5.15

⚠️ The 3.5.x branch will not receive any update—including security fixes—after 2023-12-31.

⚠️ We recently released important security updates, so if you are still using a 4.2.0 pre-release, 4.1.7 or below, 4.0.9 or below, or 3.5.13 or below, please update as soon as possible (see the release notes for v3.5.14).

End of life notice

The 3.5.x branch will not receive any update after 2023-12-31.
This means that no security fix will be made available for this branch after this date, and you will need to update to a more recent version (such as the 4.1.x branch) to receive security fixes.

Changelog

Changed

• Change user archive export allowed period from 7 days to 6 days (suddjian)

Fixed

• Fix mentions being matched in some URL query strings (mjankowski)
• Fix importer returning negative row estimates (jgillich)
• Fix filtering audit log for entries about disabling 2FA (ClearlyClaire)
• Fix tIME chunk not being properly removed from PNG uploads (TheEssem)
• Fix inefficient queries in “Follows and followers” as well as several admin pages (ClearlyClaire, ClearlyClaire)

Upgrade notes

To get the code for v3.5.15, use git fetch && git checkout v3.5.15.

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 v3.5.13, 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: >= 12.22, < 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 3.5.14.

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

v4.2.0

We are excited to release Mastodon 4.2.0, our next major upgrade 🎉

In this version, we've added (opt-in) search for posts, along with a refined set of privacy options where users can decide whether to have their content indexed for discovery. There are also many other small improvements across the user interface that come together to make everything much more polished and smooth to get started.

To get an overview of what this release brings, check out our announcement blog post.

⚠️ We recently released important security updates.

If you don't want or can't update to 4.2.0 yet, the security updates are also available for the 4.1.x branch, the 4.0.x branch and the 3.5.x branch.

Upgrade overview

This release contains upgrade notes that deviate from the norm:

ℹ️ Requires streaming API restart
ℹ️ Requires database migrations
ℹ️ Starting from this release, Mastodon will periodically check for updates (see below if you want to disable that behavior)
⚠️ Requires rebuilding Elasticsearch indexes
⚠️ The minimal supported version for Ruby has been bumped to 3.0
⚠️ The minimal supported version for Node.js has been bumped to 16
⚠️ The minimal supported version for PostgreSQL has been bumped to 10. Please note that using PostgreSQL 10 or 11 is deprecated and will not be supported in 4.3.0.
⚠️ The minimal supported version for LibreTranslate has been bumped to 1.3.3
⚠️ The way database replicas are configured has changed
⚠️ Disables part of the StatsD integration by default
⚠️ Drops built-in clustering support from the streaming server
⚠️ Updated systemd unit files for the streaming server
⚠️ We will stop bundling PgHero in a future release

For more information, scroll down to the upgrade instructions section.

Changelog

The following changelog entries focus on changes visible to users, administrators, client developers or federated software developers, but there has also been a lot of code modernization, refactoring, and tooling work, in particular by @danielmbrasil, @mjankowski, @nschonni, @renchap, and @takayamaki.

Added

• Add full-text search of opted-in public posts and rework search operators (Gargron, jsgoldstein, ClearlyClaire, ClearlyClaire, jsgoldstein, Gargron, Gargron, Gargron, Gargron, Gargron, Gargron, Gargron, ClearlyClaire, Gargron, Gargron, ClearlyClaire, ClearlyClaire, ClearlyClaire, Gargron, ClearlyClaire, Gargron, Gargron, Gargron, ClearlyClaire, Gargron, Gargron, Gargron, Gargron, Gargron, arbolitoloco1, tribela, ClearlyClaire, ClearlyClaire, ClearlyClaire)
  This introduces a new public_statuses Elasticsearch index for public posts by users who have opted in to their posts being searchable (toot#indexable flag).
  This also revisits the other indexes to provide more useful indexing, and adds new search operators such as from:me, before:2022-11-01, after:2022-11-01, during:2022-11-01, language:fr, has:poll, or in:library (for searching only in posts you have written or interacted with).
  Results are now ordered chronologically.
• Add admin notifications for new Mastodon versions (ClearlyClaire)
  This is done by querying https://api.joinmastodon.org/update-check every 30 minutes in a background job.
  That URL can be changed using the UPDATE_CHECK_URL environment variable, and the feature outright disabled by setting that variable to an empty string (UPDATE_CHECK_URL=).
• Add “Privacy and reach” tab in profile settings (Gargron, ClearlyClaire)
  This reorganized scattered privacy and reach settings to a single place, as well as improve their wording.
• Add display of out-of-band hashtags in the web interface (Gargron, arbolitoloco1, ClearlyClaire, ClearlyClaire, ClearlyClaire, Gargron, ClearlyClaire)
• Add role badges to the web interface (ClearlyClaire, Gargron)
• Add ability to pick domains to forward reports to using the forward_to_domains parameter in POST /api/v1/reports (ClearlyClaire, ClearlyClaire)
  The forward_to_domains REST API parameter is a list of strings. If it is empty or omitted, the previous behavior is maintained.
  The forward parameter still needs to be set for forward_to_domains to be taken into account.
  The forwarded-to domains can only include that of the original author and people being replied to.
• Add forwarding of reported replies to servers being replied to (Gargron, ClearlyClaire)
• Add ONE_CLICK_SSO_LOGIN environment variable to directly link to the Single-Sign On provider if there is only one sign up method available (CSDUMMI, ClearlyClaire, CSDUMMI, ClearlyClaire)
• Add webhook templating (Gargron)
• Add webhooks for local status.created, status.updated, account.updated and report.updated (VyrCossont, VyrCossont, VyrCossont)
• Add exclusive lists (dariusk, necropolina, ClearlyClaire)
• Add a confirmation screen when suspending a domain (ClearlyClaire, ClearlyClaire)
• Add support for importing lists (ClearlyClaire, mgmn, ClearlyClaire)
• Add optional hCaptcha support (ClearlyClaire, ClearlyClaire, Gargron, ClearlyClaire)
• Add lines to threads in web UI (Gargron, ClearlyClaire, ClearlyClaire, ClearlyClaire, ClearlyClaire, ClearlyClaire, ClearlyClaire, [ClearlyClaire](https://github.com/mastodon/mast...

v4.1.9

This release addresses an issue that was introduced by the last security update and includes changelogs for both updates.

⚠️ This is a follow-up to the important 4.1.8 security update that fixed major security issues (CVE-2023-42451, CVE-2023-42452).

Corresponding security releases are available for the 4.0.x branch and the 3.5.x branch.
If you are using nightly builds, do not use this release but update to nightly.2023-09-20 or newer instead. If you are on the main branch, update to the latest commit.

Changelog (v4.1.9)

Fixed

• Fix post translation erroring out (ClearlyClaire)

Changelog (v4.1.8)

Fixed

• Fix post edits not being forwarded as expected (ClearlyClaire)
• Fix moderator rights inconsistencies (ClearlyClaire)
• Fix crash when encountering invalid URL (ClearlyClaire)
• Fix cached posts including stale stats (ClearlyClaire)
• Fix uploading of video files for which ffprobe reports 0/0 average framerate (NicolaiSoeborg)
• Fix unexpected audio stream transcoding when uploaded video is eligible to passthrough (yufushiro)

Security

• Fix missing HTML sanitization in translation API (CVE-2023-42452, GHSA-2693-xr3m-jhqr)
• Fix incorrect domain name normalization (CVE-2023-42451, GHSA-v3xf-c9qf-j667)

Upgrade notes

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

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.7 or 4.1.8.

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

v4.0.11

⚠️ The 4.0.x branch will not receive any update—including security fixes—after 2023-10-31.

This release addresses an issue that was introduced by the last security update and includes changelogs for both updates.

⚠️ This is a follow-up to the important 4.0.10 security update that fixed major security issues (CVE-2023-42451, CVE-2023-42452).

Corresponding security releases are available for the 4.1.x branch and the 3.5.x branch.

End of life notice

The 4.0.x branch will not receive any update after 2023-10-31.
This means that no security fix will be made available for this branch after this date, and you will need to update to a more recent version (such as the 4.1.x branch) to receive security fixes.

Changelog (v4.0.11)

Fixed

• Fix post translation erroring out (ClearlyClaire)

Changelog (v4.0.10)

Fixed

• Fix moderator rights inconsistencies (ClearlyClaire)
• Fix crash when encountering invalid URL (ClearlyClaire)
• Fix cached posts including stale stats (ClearlyClaire)
• Fix uploading of video files for which ffprobe reports 0/0 average framerate (NicolaiSoeborg)
• Fix unexpected audio stream transcoding when uploaded video is eligible to passthrough (yufushiro)

Security

• Fix missing HTML sanitization in translation API (CVE-2023-42452, GHSA-2693-xr3m-jhqr)
• Fix incorrect domain name normalization (CVE-2023-42451, GHSA-v3xf-c9qf-j667)

Upgrade notes

To get the code for v4.0.11, use git fetch && git checkout v4.0.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.0.9, 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.0.9 or 4.0.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

v4.2.0-rc2

⚠️ This is a pre-release! This has not been as widely tested as regular releases, although it is still tested on mastodon.social and some other servers. If you update to this release, you will not be able to safely downgrade to the existing stable releases. You will, however, be able to upgrade to later nightly releases as well as the upcoming 4.2.0 stable release.

⚠️ This release is an important security release fixing major security issues (CVE-2023-42451, CVE-2023-42452, CVE-2023-42450).

Corresponding security releases are available for the 4.1.x branch, the 4.0.x branch and the 3.5.x branch.

Upgrade overview

This release contains upgrade notes that deviate from the norm:

ℹ️ Requires streaming API restart
ℹ️ Requires database migrations
ℹ️ Starting from this release, Mastodon will periodically check for updates (see below if you want to disable that behavior)
⚠️ Requires rebuilding Elasticsearch indexes
⚠️ The minimal supported version for Ruby has been bumped to 3.0
⚠️ The minimal supported version for Node.js has been bumped to 16
⚠️ The minimal supported version for PostgreSQL has been bumped to 10. Please note that using PostgreSQL 10 or 11 is deprecated and will not be supported in 4.3.0.
⚠️ The minimal supported version for LibreTranslate has been bumped to 1.3.3
⚠️ The way database replicas are configured has changed
⚠️ Disables part of the StatsD integration by default
⚠️ Drops built-in clustering support from the streaming server
⚠️ Updated systemd unit files for the streaming server
⚠️ A configuration change is required for some S3-compatible storage providers
⚠️ We will stop bundling PgHero in a future release

For more information, scroll down to the upgrade instructions section.

Changelog (v4.2.0-rc2)

Added

• Add additional metrics for streaming (ThisIsMissEm)

Changed

• Change video bitrate to always fit within size limit (Gargron)

Fixed

• Fix hashtag bar being sometimes incorrectly hidden (ClearlyClaire)
• Fix crash when viewing a moderation appeal and the moderator account has been deleted (xrobau)
• Fix Web UI making duplicate search queries when scrolling (ClearlyClaire)
• Fix error in Web UI when server rules cannot be fetched (ClearlyClaire)
• Fix Setting.authorized_fetch not being properly taken into consideration (ClearlyClaire)
• Fix post edits not being forwarded as expected (ClearlyClaire)
• Fix dismiss button overlapping with text in dismissable banners (ClearlyClaire)
• Fix obsolete cache key in status cache invalidation logic (ClearlyClaire)
• Fix processing of min_id and max_id parameters in /api/v2/search (ClearlyClaire)

Security

• Fix incorrect URL normalization (CVE-2023-42450, GHSA-hcqf-fw2r-52g4)
• Fix missing HTML sanitization in translation API (CVE-2023-42452, GHSA-2693-xr3m-jhqr)
• Fix incorrect domain name normalization (CVE-2023-42451, GHSA-v3xf-c9qf-j667)

Changelog (v4.2.0-rc1)

Added

• Add full-text search of opted-in public posts and rework search operators (Gargron, jsgoldstein, ClearlyClaire, ClearlyClaire, jsgoldstein, Gargron, Gargron, Gargron, Gargron, Gargron, Gargron, Gargron, ClearlyClaire, Gargron, Gargron, ClearlyClaire, ClearlyClaire, ClearlyClaire, Gargron, ClearlyClaire, Gargron, Gargron, Gargron, ClearlyClaire, Gargron, Gargron, Gargron, Gargron, Gargron, arbolitoloco1, tribela)
  This introduces a new public_statuses Elasticsearch index for public posts by users who have opted in to their posts being searchable (toot#indexable flag).
  This also revisits the other indexes to provide more useful indexing, and adds new search operators such as from:me, before:2022-11-01, after:2022-11-01, during:2022-11-01, language:fr, has:poll, or in:library (for searching only in posts you have written or interacted with).
  Results are now ordered chronologically.
• Add admin notifications for new Mastodon versions (ClearlyClaire)
  This is done by querying https://api.joinmastodon.org/update-check every 30 minutes in a background job.
  That URL can be changed using the UPDATE_CHECK_URL environment variable, and the feature outright disabled by setting that variable to an empty string (UPDATE_CHECK_URL=).
• Add “Privacy and reach” tab in profile settings (Gargron, ClearlyClaire)
  This reorganized scattered privacy and reach settings to a single place, as well as improve their wording.
• Add display of out-of-band hashtags in the web interface (Gargron, arbolitoloco1, ClearlyClaire, ClearlyClaire, ClearlyClaire, Gargron)
• Add role badges to the web interface (ClearlyClaire, Gargron)
• Add ability to pick domains to forward reports to using the forward_to_domains parameter in POST /api/v1/reports (ClearlyClaire, ClearlyClaire)
  The forward_to_domains REST API parameter is a list of strings. If it is empty or omitted, the previous behavior is maintained.
  The forward parameter still needs to be set for forward_to_domains to be taken into account.
  The forwarded-to domains can only include that of the original author and people being replied to.
• Add forwarding of reported replies to servers being replied to (Gargron, ClearlyClaire)
• Add ONE_CLICK_SSO_LOGIN environment variable to directly link to the Single-Sign On provider if there is only one sign up method available (CSDUMMI, ClearlyClaire, CSDUMMI, ClearlyClaire)
• Add webhook templating (Gargron)
• Add webhooks for local status.created, status.updated, account.updated and report.updated (VyrCossont, VyrCossont, VyrCossont)
• Add exclusive lists (dariusk, necropolina, ClearlyClaire)
• **Add a confirmation screen when s...

v4.1.8

⚠️ This release is an important security release fixing major security issues (CVE-2023-42451, CVE-2023-42452).

Corresponding security releases are available for the 4.0.x branch and the 3.5.x branch.
If you are using nightly builds, do not use this release but update to nightly.2023-09-20 or newer instead. If you are on the main branch, update to the latest commit.

Changelog

Fixed

• Fix post edits not being forwarded as expected (ClearlyClaire)
• Fix moderator rights inconsistencies (ClearlyClaire)
• Fix crash when encountering invalid URL (ClearlyClaire)
• Fix cached posts including stale stats (ClearlyClaire)
• Fix uploading of video files for which ffprobe reports 0/0 average framerate (NicolaiSoeborg)
• Fix unexpected audio stream transcoding when uploaded video is eligible to passthrough (yufushiro)

Security

• Fix missing HTML sanitization in translation API (CVE-2023-42452, GHSA-2693-xr3m-jhqr)
• Fix incorrect domain name normalization (CVE-2023-42451, GHSA-v3xf-c9qf-j667)

Upgrade notes

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

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.7.

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

v4.0.10

⚠️ The 4.0.x branch will not receive any update—including security fixes—after 2023-10-31.

⚠️ This release is an important security release fixing major security issues (CVE-2023-42451, CVE-2023-42452).

Corresponding security releases are available for the 4.1.x branch and the 3.5.x branch.
If you are using nightly builds, do not use this release but update to nightly.2023-09-20 or newer instead. If you are on the main branch, update to the latest commit.

End of life notice

The 4.0.x branch will not receive any update after 2023-10-31.
This means that no security fix will be made available for this branch after this date, and you will need to update to a more recent version (such as the 4.1.x branch) to receive security fixes.

Changelog

Fixed

• Fix moderator rights inconsistencies (ClearlyClaire)
• Fix crash when encountering invalid URL (ClearlyClaire)
• Fix cached posts including stale stats (ClearlyClaire)
• Fix uploading of video files for which ffprobe reports 0/0 average framerate (NicolaiSoeborg)
• Fix unexpected audio stream transcoding when uploaded video is eligible to passthrough (yufushiro)

Security

• Fix missing HTML sanitization in translation API (CVE-2023-42452, GHSA-2693-xr3m-jhqr)
• Fix incorrect domain name normalization (CVE-2023-42451, GHSA-v3xf-c9qf-j667)

Upgrade notes

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

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.0.9, 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.0.9.

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