@Gargron Gargron released this Oct 25, 2018 · 212 commits to master since this release

Assets 2


Note: This is a release candidate. It is intended to be stable, but not guaranteed.


  • Add suggested follows to search screen in mobile layout (#9010)

Note: The suggestions API has been added in 2.5.0. They are filled by your own actions and nothing else. For example, if I see a lot of a certain cat on my feed boosted by other people, and I re-boost it often enough, my suggestion will be to follow that particular cat, to go straight to the source so to speak. Same for favouriting, and to a lesser extent, replying. A button next to each suggestion lets you remove that suggestion instantly.

  • Add CORS header to /.well-known/* routes (#9083)
  • Change docker-compose default to persist volumes in current directory (#9055)


  • Fix domain label position and color (#9033)
  • Fix RTL column settings toggle label (#9037)
  • Fix RTL admin account avatar margin in about page (#9039)
  • Fix RTL cardbar margins and alignment (#9044)
  • Fix tootctl accounts cull on dead servers (#9041)
  • Fix tootctl accounts cull tripping on nil in last_webfingered_at (#9051)
  • Fix public timelines not instantly updating on compose (#9050)
  • Fix crash when using UNIX socket (#9036)
  • Fix crash if username is not found on tootctl feeds build (#9040)
  • Fix og:url on status pages (#9047)
  • Fix upload option buttons only being visible on hover (#9074)
  • Fix JS error when posting from page without router context (#9073)
  • Fix RTL layout of status display names (#9075)
  • Fix missing plural keys (#9084)
  • Fix RTL layout not applying in admin UI (#9081)
  • Migrate all old direct messages to new conversations schema (#9085)

Upgrade notes:

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

This release candidate adds a migration that will insert all pre-existing direct messages into the revamped direct messages schema. It has to iterate over a potentially large data set, so that migration may take a while. It will not lock the tables, so it is safe to run for a very long time without bringing your Mastodon web process down (in fact, database migrations never warrant downtime unless explicitly stated, but I know that some people do that...). You will have 10 seconds to interrupt the migration if you don't want to run it.

Non-Docker only:

  • Install dependencies: bundle 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

Contributors to this release: