Immich 1.136 Photo and Video Backup Brings Breaking Changes
Immich 1.136 Photo and Video Backup Brings Breaking Changes
linuxiac.com
Immich 1.136 Photo and Video Backup Brings Breaking Changes
32 comments
-
-
The one feature I've been waiting on for a while is better face recognition in videos, not only the first frame. When/if this happens I will start using it. They're discussing it for quite a while though, afraid it won't happen.
-
I'm still using photoprism. Or sort of rarely using it. So how's immich in comparison now?
-
As the title might appear a bit alarmist, saving a click "For most users, there’s nothing to worry about. However, if you’ve manually set a custom relative path for “IMMICH_MEDIA_LOCATION” in your “.env” file, you’ll need to convert it to an absolute path. For example, “IMMICH_MEDIA_LOCATION=./my-library” must become “IMMICH_MEDIA_LOCATION=/usr/src/app/my-library“."
-
How is it alarmist? Those are breaking changes that require attention
-
I wouldn't think this would cause any data loss either, it just wouldn't find your media or it would throw an error. Very alarmist indeed.
-
I'm not sure it's alarmist; I think this is all a breaking change is.
Anybody updating needs to know their existing config may not longer be supported. Even if the consequences are small, even if not every user will be affected, this update will break some previously acceptable configs. I think that warrants a heads up and a reminder to read the release notes.
-
Also, Immich warns to read the change log every time you update, because it's still under very active development.
-
-
-
The new beta timeline is sooo smooth! I finally don't hate scrolling back to find a specific old photo. The scrolling performance feels completely native to me now.
-
Actual release notes: https://github.com/immich-app/immich/releases/tag/v1.136.0
-
The Android app finally does IO on a background thread. 🫠
-
I've been meaning to give this a try on my Synology.
But breaking changes in a point release? Not cool.
-
The “breaking change” did not break anything for me. As noted, you have to have a specific and non-default configuration for their to be a problem.
-
Tbf this is actually version v1.136 .0 and
Disclaimer
- ⚠️ The project is under very active development.
- ⚠️ Expect bugs and breaking changes.
- ⚠️ Do not use the app as the only way to store your photos and videos.
- ⚠️ Always follow 3-2-1 backup plan for your precious photos and videos!
-
Personally I’m waiting for the day it comes out of “under active development” state so that I can migrate from NextCloud to it.
-
A breaking change should have been 2.0, not a new 1.
<minor>
release.It should still be 0.
<minor>
if they've not reached the stability for keeping backwards compatibly in all 1.x releases.
-
From the release notes:
one of the last breaking changes we want to make before reaching the stable release milestone
So you'll probably want to wait until they do a stable release.
-
Yes indeed. 🙂
-
-
It's a full release, not a point/patch release, the title just doesn't show the second .0. They use semantic versioning so it's major.minor.patch.
It's also a very minor change and only affects a single configuration property and only people who used relative paths in that property.
-
Breaking changes should warrant a 2.0 version, not a 1.minor version.
Edit: I am basing my comments on https://semver.org/ guidelines
-
-
32 comments
For what it is worth, I upgraded without changing anything and it worked perfectly.