v4.0.2-ls14

LinuxServer Changes:

Updated nginx conf to fix bring inline with Mastodon configuration (fixes Elk integration).

mastodon Changes:

Changelog

Fixed

• Fix wrong color on mentions hidden behind content warning in web UI (Gargron)
• Fix filters from other users being used in the streaming service (ClearlyClaire)
• Fix unsafe-eval being used when wasm-unsafe-eval is enough in Content Security Policy (Gargron, prplecake)

Upgrade notes

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

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

Update steps

The following instructions are for updating from 4.0.0 or 4.0.1.

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. You can use the 4.0.0 upgrade notes to upgrade directly to 4.0.2.

Non-Docker only:

• Install dependencies: bundle install

Both Docker and non-Docker:

1. Precompile the assets:
   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step
2. Restart all Mastodon processes

develop-v4.1.0rc2-ls16

LinuxServer Changes:

Add aliases for key generation & tootctl to better support secrets.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

v4.0.2-ls13

LinuxServer Changes:

Updated nginx conf to fix bring inline with Mastodon configuration (fixes Elk integration).

mastodon Changes:

Changelog

Fixed

• Fix wrong color on mentions hidden behind content warning in web UI (Gargron)
• Fix filters from other users being used in the streaming service (ClearlyClaire)
• Fix unsafe-eval being used when wasm-unsafe-eval is enough in Content Security Policy (Gargron, prplecake)

Upgrade notes

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

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

Update steps

The following instructions are for updating from 4.0.0 or 4.0.1.

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. You can use the 4.0.0 upgrade notes to upgrade directly to 4.0.2.

Non-Docker only:

• Install dependencies: bundle install

Both Docker and non-Docker:

1. Precompile the assets:
   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step
2. Restart all Mastodon processes

develop-v4.1.0rc2-ls15

LinuxServer Changes:

Add aliases for key generation & tootctl to better support secrets.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

develop-v4.1.0rc2-ls14

LinuxServer Changes:

Add aliases for key generation & tootctl to better support secrets.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

v4.0.2-ls12

LinuxServer Changes:

Updated nginx conf to fix bring inline with Mastodon configuration (fixes Elk integration).

mastodon Changes:

Changelog

Fixed

• Fix wrong color on mentions hidden behind content warning in web UI (Gargron)
• Fix filters from other users being used in the streaming service (ClearlyClaire)
• Fix unsafe-eval being used when wasm-unsafe-eval is enough in Content Security Policy (Gargron, prplecake)

Upgrade notes

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

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

Update steps

The following instructions are for updating from 4.0.0 or 4.0.1.

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. You can use the 4.0.0 upgrade notes to upgrade directly to 4.0.2.

Non-Docker only:

• Install dependencies: bundle install

Both Docker and non-Docker:

1. Precompile the assets:
   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step
2. Restart all Mastodon processes

develop-v4.1.0rc2-ls13

LinuxServer Changes:

Support separate sidekiq queue instances.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

develop-v4.1.0rc1-ls12

LinuxServer Changes:

Support separate sidekiq queue instances.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

develop-v4.1.0rc1-ls11

LinuxServer Changes:

Support separate sidekiq queue instances.

Remote Changes:

Data change at JSON endpoint https://api.github.com/repos/mastodon/mastodon/releases

v4.0.2-ls11

LinuxServer Changes:

Updated nginx conf to fix bring inline with Mastodon configuration (fixes Elk integration).

mastodon Changes:

Changelog

Fixed

• Fix wrong color on mentions hidden behind content warning in web UI (Gargron)
• Fix filters from other users being used in the streaming service (ClearlyClaire)
• Fix unsafe-eval being used when wasm-unsafe-eval is enough in Content Security Policy (Gargron, prplecake)

Upgrade notes

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

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

Update steps

The following instructions are for updating from 4.0.0 or 4.0.1.

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. You can use the 4.0.0 upgrade notes to upgrade directly to 4.0.2.

Non-Docker only:

• Install dependencies: bundle install

Both Docker and non-Docker:

1. Precompile the assets:
   • Non-Docker: RAILS_ENV=production bundle exec rails assets:precompile
   • Docker: The assets are already precompiled during the build step
2. Restart all Mastodon processes