Post #988930
2026-03-30 12:50 UTC
Replies (5)
-
@treuss@metalhead.club 2026-03-30 15:00
Oh, I just found this in the docs: "You can safely skip deploying every single PATCH level (see above) version release when upgrading from an old version. You do not need to individually deploy them all. However, you should deploy at least one release from every MINOR version series. Most importantly, keep track of the instructions with each release or collection of releases. Most instructions overlap, you just need to make sure you execute everything at least once." I have no idea how I could have missed that. src: https://docs.joinmastodon.org/admin/upgrading/
-
@treuss@metalhead.club 2026-03-31 14:36
Thanks everyone for your help. I was able to finally update the instance from v4.3.21 to v4.5.8.
-
@danny@strangeminds.social 2026-03-30 13:03
@treuss I'm no expert, but in my opinion, if you don't want to brick your system, I'd upgrade sequentially from v4.3.21
-
@michael@mstdn.thms.uk 2026-03-30 14:36
@treuss Yeah, I don't think this should be a problem. Just make sure you read and understand the release notes of every skipped release: many will contain upgrade steps, and you will need to perform all upgrade steps (even those for skipped steps) in the correct order at the end. E.g. 4.4 requires a re-index of Elasticsearch (if you have that enabled). You don't need to stop at 4.4 and execute that there: You can do it on 4.5, but you cannot skip it. Why not go directly to 4.5.8 though?
-
@adam@fedi.adamm.cc 2026-03-30 16:21
@treuss TL.DR: Read through all release notes and perform all steps unique to each set of notes, as well as all steps common to all release notes. You can do a direct upgrade, but only if all of the release notes for each upgrade shows that the steps are the same. The real big thing is pre and post migrations. You must do these for most anything major. However, some versions require extra steps beyond these, and they would need to be completed during the upgrade to the final target release, even if they do not apply to that release. For example, a while ago, some secrets were required to be added to the env.production file. Many mastoadmins got caught here, as they would have skipped the version requiring these keys added, and then they would not have seen this requirement in the final release notes of the target version they were upgrading to, and thus would have resulted in a broken installation until this step was completed.