v1.95.0
Warning
⚠️ Breaking Changes ⚠️
1. Upgrade pgvecto.rs to stable version 0.2.0 for enhanced search
Step 1: Change the docker-compose.yml database image from 0.1.11 to 0.2.0
[...]
database...
For the exact reason they are posting this. What if some service you are referencing has breaking changes? If you pinpoint the exact version it will have no effect to your project unless you decide (hopefully after some consideration) to upgrade the service version number.
Which clearly requires user interaction, why not take that out of users’ hands and just have
image: tensorchord/pgvecto-rs:latest-stable
Which is effectively what they’re using anyway? I can understand freezing on a version when the upstream removes a feature, but that’s not happened and even so, why do they need the SHA verification? Sorry if it seems stupid and straight forward, this is the only container I host that does this and so I’m trying to understand it rather than just feel aggrieved by it.
pgvecto.rs is a Postgres extension that provides vector similarity search functions. It is written in Rust and based on pgrx. It is currently in the beta status, we invite you to try it out in production and provide us with feedback. Read more at 📝our blog.
Because there is no stable release. Any update can have breaking changes since it is beta software like immich itself.
Also, it’s best practise to specifically refer to the digest for containers to avoid re-tags resulting in different images. For folks who audit what runs on their infrastructure, digests are the standard way of referring to an image. For Immich, I’d presume that the digest is partially a security thing and partially a “this specific image is known to be working”.
I wondered about the sha as well but that’s good if you really depend on that version. Since immich is still heavily developing, this isn’t something I’d focus in the short term. Only if it persists
For the exact reason they are posting this. What if some service you are referencing has breaking changes? If you pinpoint the exact version it will have no effect to your project unless you decide (hopefully after some consideration) to upgrade the service version number.
Sorry, I think I’m asking my question poorly, what I mean is instead of
Which clearly requires user interaction, why not take that out of users’ hands and just have
Which is effectively what they’re using anyway? I can understand freezing on a version when the upstream removes a feature, but that’s not happened and even so, why do they need the SHA verification? Sorry if it seems stupid and straight forward, this is the only container I host that does this and so I’m trying to understand it rather than just feel aggrieved by it.
Because there is no stable release. Any update can have breaking changes since it is beta software like immich itself.
Thank you very much. I looked at their Github and saw a couple channels for releases and made a poor assumption. Thanks for sharing your insight.
Also, it’s best practise to specifically refer to the digest for containers to avoid re-tags resulting in different images. For folks who audit what runs on their infrastructure, digests are the standard way of referring to an image. For Immich, I’d presume that the digest is partially a security thing and partially a “this specific image is known to be working”.
Thank you very much for teaching me something new
I wondered about the sha as well but that’s good if you really depend on that version. Since immich is still heavily developing, this isn’t something I’d focus in the short term. Only if it persists
Ah okay. Thank you for making the time to respond.