Upgrade to v3.3.0. They messed up the Git history, so simply merging 3.3.0 into our production branch leads to a ton of conflicts. The easier solution is therefore to branch out fresh and cherry-pick our custom changes.
Upgrade to v3.3.0. They messed up the Git history, so simply merging 3.3.0 into our production branch leads to a ton of conflicts. The easier solution is therefore to branch out fresh and cherry-pick our custom changes.
The deployment needs to be half-manual, as there are pre- and post-build migrations to run. See upgrade notes in https://github.com/tootsuite/mastodon/releases/tag/v3.3.0
Upgrade to v3.3.0. They messed up the Git history, so simply merging 3.3.0 into our production branch leads to a ton of conflicts. The easier solution is therefore to branch out fresh and cherry-pick our custom changes.
The deployment needs to be half-manual, as there are pre- and post-build migrations to run. See upgrade notes in https://github.com/tootsuite/mastodon/releases/tag/v3.3.0