LinuxServer Changes:

Add Glitch branch.

mastodon Changes:

Changelog

Added

• Add redirection from paths with url-encoded @ to their decoded form (thijskh)
• Add lang attribute to native language names in language picker in Web UI (ClearlyClaire)
• Add headers to outgoing mails to avoid auto-replies (ClearlyClaire)
• Add support for refreshing many accounts at once with tootctl accounts refresh (9p4)
• Add confirmation modal when clicking to edit a post with a non-empty compose form (PauloVilarinho)
• Add support for the HAproxy PROXY protocol through the PROXY_PROTO_V1 environment variable (CSDUMMI)
• Add SENDFILE_HEADER environment variable (Gargron)
• Add cache headers to static files served through Rails (Gargron)

Changed

• Increase contrast of upload progress bar background (toolmantim)
• Change post auto-deletion throttling constants to better scale with server size (ClearlyClaire)
• Change order of bookmark and favourite sidebar entries in single-column UI for consistency (TerryGarcia)
• Change ActivityPub::DeliveryWorker retries to be spread out more (ClearlyClaire)

Fixed

• Fix “Remove all followers from the selected domains” also removing follows and notifications (ClearlyClaire)
• Fix streaming metrics format (emilweth, emilweth)
• Fix case-sensitive check for previously used hashtags in hashtag autocompletion (deanveloper)
• Fix focus point of already-attached media not saving after edit (ClearlyClaire)
• Fix sidebar behavior in settings/admin UI on mobile (wxt2005)
• Fix inefficiency when searching accounts per username in admin interface (ClearlyClaire)
• Fix duplicate “Publish” button on mobile (ClearlyClaire)
• Fix server error when failing to follow back followers from /relationships (ClearlyClaire)
• Fix server error when attempting to display the edit history of a trendable post in the admin interface (ClearlyClaire)
• Fix tootctl accounts migrate crashing because of a typo (ClearlyClaire)
• Fix original account being unfollowed on migration before the follow request to the new account could be sent (ClearlyClaire)
• Fix the “Back” button in column headers sometimes leaving Mastodon (c960657)
• Fix pgBouncer resetting application name on every transaction (Gargron)
• Fix unconfirmed accounts being counted as active users (ClearlyClaire)
• Fix /api/v1/streaming sub-paths not being redirected (ClearlyClaire)
• Fix drag'n'drop upload area text that spans multiple lines not being centered (vintprox)
• Fix sidekiq jobs not triggering Elasticsearch index updates (ClearlyClaire)
• Fix tags being unnecessarily stripped from plain-text short site description (c960657)
• Fix HTML entities not being un-escaped in extracted plain-text from remote posts (c960657)
• Fix dashboard crash on ElasticSearch server error (ClearlyClaire)
• Fix incorrect post links in strikes when the account is remote (ClearlyClaire)
• Fix misleading error code when receiving invalid WebAuthn credentials (ClearlyClaire)
• Fix duplicate mails being sent when the SMTP server is too slow to close the connection (ClearlyClaire)

Security

• Change user backups to use expiring URLs for download when possible (Gargron)
• Add warning for object storage misconfiguration (ClearlyClaire)

Upgrade notes

To get the code for v4.1.1, use git fetch && git checkout v4.1.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 compared to v4.1.0, 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 or higher

Update steps

The following instructions are for updating from 4.1.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:

• Install dependencies: bundle install and yarn install

Both Docker and non-Docker:

1. Run the database migrations:
   • Non-Docker: RAILS_ENV=production bundle exec rails db:migrate
   • Docker: docker-compose run --rm web rails db:migrate
2. Precompile the assets:
   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step
3. Restart all Mastodon processes