Help me understand what "Stable" actually means when the deps are still kind of* changing
So, I have been using the immich for quite some time now, almost more than 1.5 years, and I've been keeping an eye on the compose.yml file on every release, and I understand that initially there were changes at setting up compose.yml level, like ENV vars and some other breaking changes we have noticed during that time.
But even after "Stable Release", I'm a little confused when on a new release, I see that there is a new
What I meant is "What if I just check that there is a new Immich release and I update it, but I didn't update my current compose.yml's postgresql image hash".
Can the upgrade be done without matching the image hash for both
If yes, does this define the word "stable" or does an end user have to match all the image hashes whenver they see a new immich release?
But even after "Stable Release", I'm a little confused when on a new release, I see that there is a new
PostgreSQL image hash, I know that it is not immich but what if this new hash pointer has some changes at postgresql level.What I meant is "What if I just check that there is a new Immich release and I update it, but I didn't update my current compose.yml's postgresql image hash".
Can the upgrade be done without matching the image hash for both
postgresql and redis ?If yes, does this define the word "stable" or does an end user have to match all the image hashes whenver they see a new immich release?
