Upgrade Mastodon to 3.3.0 (needs manual migration) #286

Closed
opened 2021-01-13 16:15:43 +00:00 by raucao · 0 comments
Owner

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
raucao added the
service
mastodon
label 2021-01-13 16:16:38 +00:00
raucao self-assigned this 2021-12-05 21:08:01 +00:00
greg closed this issue 2021-12-09 13:32:22 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#286
No description provided.