fix(cum-media): run immich 3 from unstable #28
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/immich-3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
cum-mediano longer evaluates: 26.05 only has immich 2.7.5, which is marked insecure and gets no more updates.The 26.05 module stays. Its differences from the unstable module don't affect this host.
Evidence
nix eval .#nixosConfigurations.cum-media.config.system.build.toplevel.drvPathAfter:Evaluation only: this has not been built or run. A dry run of immich and its machine learning package shows nothing to compile locally.
Checked on
cum-mediaagainst the immich 3.3.5 requirements:>=14>=0.3 <2>=0.5 <1sse4_2presentpublic.vectorcolumns,vchordrqindexesvectors0.3.0 (pgvecto.rs) is still registered in theimmichdatabase, but it is an unused leftover. Its files are gone from disk, and a trialDROP EXTENSIONandDROP SCHEMAsucceeded and was rolled back.Merge Danger
Door: one-way
The merge itself reverts cleanly, but deploying does not: immich migrates its database on first start, and switching NixOS generations won't undo that. Going back means the previous generation plus a database restore.
Before the first rebuild of
cum-mediafrom this:The last line also clears an existing collation mismatch (glibc 2.40 to 2.42). It isn't caused by this upgrade.
Blast Radius: immich
Only the immich service on
cum-mediachanges. Mobile apps should be updated, since the legacy timeline was removed. Scripts calling the immich API may need changes because endpoints were removed or changed, and dashboards need updating because metric names changed from underscores to dots.🤖 Generated with Claude Code