Upgrade from old releases
Upgrading after skipping many revisions can be risky. Database migrations and other code are written and tested sequentially. To make this safer, upgrades are grouped into "eras" that must be applied in order.
How to upgrade
Temporary workaround
Please note, if you are stuck at v1.138.1 (revision 227), this is due a bug on my part I will push out a fix in the next days that should solve it. I need to rework this logic a little and I plan to do so over the weekend.
If you can't wait it's safe to do the following:
touch /var/snap/immich-distribution/common/no-post-refresh-hook
snap refresh immich-distribution
rm /var/snap/immich-distribution/common/no-post-refresh-hook
Disabling the post-refresh hook is safe between version v1.138 to v1.142. If you have executed commands below and are stuck at a later revision, this should still work, but you may end up in a non stable channel. If you need help, open an issue at GitHub and I will help you.
Systems that are regularly updated should move between supported eras sequentially (for example: 1 → 2 → 3 → 4). If automatic updates have been disabled or you’ve fallen far behind and attempt to jump across eras (for example: 1 → 3), the post-refresh hook will block the upgrade to protect your data. In that case, refresh to an intermediate release from the next era, apply it, and then continue to the latest. See the news for any additional notes.
Historic Eras (stable channel)
| Era | Version | Revision | Notes |
|---|---|---|---|
| 1 | v1.142.1 | 240 | Eras implemented, we are in the middle of the VectorChord migration |
| 0 | - | - | A release before revision 240 is counted as era 0 |
To move to a specific era on the stable channel, refresh to the revision listed for that era:
Find your current revision
To see what revision (rev) you have installed, run the following command:
Example below (with real data from the stable channel)
A note about Eras
Eras are a safety feature in Immich Distribution. They prevent skipping too many versions at once, which could otherwise leave your system in an unsupported state or corrupt your database. Upstream Immich does not support large upgrade jumps; eras help protect your data by requiring sequential era-by-era upgrades. Most users who keep their systems up to date will never notice or need to care about eras.