Update docker.io/tootsuite/mastodon Docker tag to v4.7.4

Share
Update docker.io/tootsuite/mastodon Docker tag to v4.7.4
Photo by Rolf van Root / Unsplash

Patch update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow with dependency update facilitated by Mend's Renovate Bot.

This MR contains the following updates:

Package Update Change
docker.io/tootsuite/mastodon patch v4.7.3 → v4.7.4

Release Notes

mastodon/mastodon (docker.io/tootsuite/mastodon)

v4.7.4

Compare Source

Mastodon

Upgrade overview

This release contains upgrade notes that deviate from the norm:

ℹ️ Default Ruby version has been updated
ℹ️ Requires assets recompilation

For more information, view the complete release notes and scroll down to the upgrade instructions section.

Changelog

Security
  • Fix insufficient ActivityPub identifier verification (GHSA-288h-6j8h-6x5j)
  • Added security challenge e-mail to users that try to log in after long period of inactivity (#​40745 by @​jhbabon)
  • Updated dependencies, in particular to address security advisories in Ruby, NodeJS, excon, css_parser, pghero, and sanitize
Fixed

Upgrade notes

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

[!NOTE]
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.6.0.

  • Ruby: 3.3 or newer
  • PostgreSQL: 14 or newer
  • Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
  • LibreTranslate (optional, for translations): 1.3.3 or newer
  • Redis: 7.0 or newer
  • Node: 22 or newer
  • libvips: 8.13 or newer
  • FFMpeg: 5.1 or newer
Update steps

The following instructions are for updating from 4.7.3.

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. In particular, it is very important to read the 4.7.0 release notes.

Non-Docker

[!TIP]
The charlock_holmes gem may fail to build on some systems with recent versions of gcc.
If you run into this issue, try BUNDLE_BUILD__CHARLOCK_HOLMES="--with-cxxflags=-std=c++17" bundle install.

  1. If you are using rbenv, update the list of available versions and install the proper Ruby version by doing RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install in the Mastodon install directory (e.g. /home/mastodon/live)
  2. Install dependencies with bundle install and yarn install --immutable
  3. Precompile the assets: RAILS_ENV=production bundle exec rails assets:precompile
  4. Restart all Mastodon processes.
When using Docker
  1. Restart all Mastodon processes.

Read more

Me on Mastodon - This link is here for verification purposes.