feat: Add Mastodon auto-update with classifier examples

This commit is contained in:
Jeena 2026-05-02 08:42:23 +00:00
parent cf7f7a7b62
commit 6b4b74fc01
8 changed files with 205 additions and 0 deletions

View file

@ -0,0 +1,29 @@
action: manual
reason: Major version with two-step database migration, new required Sidekiq queue (ingress), environment variable changes (AUTHORIZED_FETCH replaced by DISALLOW_UNAUTHENTICATED_API_ACCESS), and systemd service file updates required.
---
## Upgrade overview
This release contains upgrade notes that deviate from the norm:
ℹ️ Requires two-step database migration process for zero-downtime deployment
ℹ️ Some migrations may take a long time to run
ℹ️ Behaviour of `AUTHORIZED_FETCH` changed
ℹ️ Requires review of Sidekiq queues in some setups (new queue: `ingress`)
ℹ️ Some server settings, like thumbnail, short description, and so on, changed and may need to be looked at
## Upgrade notes
⚠️ Incoming federated activity now uses a new `ingress` queue in Sidekiq. If you customize Sidekiq processes/queues or use an old version of the `mastodon-sidekiq.service` file, ensure that there is at least one process handling the `ingress` queue.
ℹ️ The `AUTHORIZED_FETCH` option no longer affects the REST API. To restore previous behaviour, use new environment variable `DISALLOW_UNAUTHENTICATED_API_ACCESS`.
ℹ️ Media upload of images and animated GIFs are now processed differently. Make sure your installed systemd service files are up to date.
### Non-Docker
1. Run the *pre-deployment* database migrations:
`SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate`
2. Precompile the assets: `RAILS_ENV=production bundle exec rails assets:precompile`
3. Restart all Mastodon processes.
4. Run the *post-deployment* database migrations:
`RAILS_ENV=production bundle exec rails db:migrate`