How to update Immich now that I am way behind?

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨perishthethought@lemm.ee⁩ to ⁨selfhosted@lemmy.world⁩

I have Immich Server Version: v1.115.0. They’re up to v1.129.0. I am guessing there have been lots of breaking changes in that range, since that was true the last time I updated.

Is there a safe way now to update without making me read all the release notes and carefully craft my docker compose file in multiple steps to make sure I don’t lose anything in the process of getting caught up?

Thanks for any tips.

(Side note: Mannnn, do I wish they would use semantic versioning so I can tell what’s a breaking change just from the version number…)

source

Comments

Sort:hotnew top

AustralianSimon@lemmy.world ⁨1⁩ ⁨year⁩ ago
You’re going to have to read every single release with breaking changes.

source
enemenemu@lemm.ee ⁨1⁩ ⁨year⁩ ago
I just update. If it breaks, I read the notes. Probably the wrong way but it worked. And I use it for a long time. To me, it was never that unstable. And since a couple of months it’s very stable. Backup first.

source
MentalEdge@sopuli.xyz ⁨1⁩ ⁨year⁩ ago
I’d take a backup, first, and then just send it. Then, if that doesn’t work out, do it the hard and slow way.

source
tvcvt@lemmy.ml ⁨1⁩ ⁨year⁩ ago
I just had to do this. Don’t skip the release notes. They’re really good at highlighting potential pitfalls, just scroll back through and look for the heading “Breaking Changes.”

In my case there were a few, but they were only for API calls I’m not using, so I just did the update in one go and it worked out great. (Of course, I made sure to take a backup first.)

source