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...
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!
Yes project does not follow semantic versioning. But you can consider it it the 0.y.z state where it is even in the semantic versioning allowed to have breaking changes without major version increase.
I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they’re worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.
Absolutely agree with you. Just because the Versioning looks like x.y.z does not mean it follows that convention.
The most prominent example is probably the Linux Kernel Versioning.
Read the notes of the dev team and subscribe to the changelog or update channel.
Hot take? This should have been a major version update.
https://semver.org/
Yes project does not follow semantic versioning. But you can consider it it the 0.y.z state where it is even in the semantic versioning allowed to have breaking changes without major version increase.
There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver.
I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they’re worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.
Absolutely agree with you. Just because the Versioning looks like x.y.z does not mean it follows that convention. The most prominent example is probably the Linux Kernel Versioning.
Read the notes of the dev team and subscribe to the changelog or update channel.