GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
Change remote report processing to accept reports with long comments, but truncate them (ThisIsMissEm)
Fixed
Fix blocking subdomains of an already-blocked domain (ClearlyClaire)
Fix /api/v1/timelines/tag/:hashtag allowing for unauthenticated access when public preview is disabled (danielmbrasil)
Fix inefficiencies in PlainTextFormatter (ClearlyClaire)
Upgrade notes
To get the code for v4.1.7, use git fetch && git checkout v4.1.7.
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.6, 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.6.
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:
Restart all Mastodon processes
Configuration
Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
Automerge: Disabled by config. Please merge this manually once you are satisfied.
Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.
Ignore: Close this MR and you won't be reminded about this update again.
If you want to rebase/retry this MR, check this box
