Repository navigation
VecturaDB 1.0.0-preview.5: the passages to the latest release, and the post-releases of the previews - #19
Merged
Conversation
ambergrove
approved these changes
Oct 28, 2026
ambergrove
approved these changes
Nov 3, 2026
… the order of SemVer VecturaDB tags a post-release of a preview as vX.Y.Z-preview.N.postM, like 1.0.0-preview.3.post1, its latest release, which the operator refused. A post-release comes after its preview and before the next one, as in SemVer 2.0; post-releases compare by number, as in PEP 440. A post-release of a release, or without its number, is still refused. The examples of the CRD name the latest release.
Three rows of the table, from Chroma 1.5.9, from VecturaDB 1.0.0-preview.2 and from 1.0.0-preview.3, after the trials of 1.0.0-preview.3 on a k3d volume with the post-release, plus two cases from 1.0.0-preview.3: two runs with the same outcome, the same as with 1.0.0-preview.3. The README and the end-to-end tests use the latest release.
Five rows of the table, to 1.0.0-preview.5, the latest release: from Chroma 1.5.9 and from VecturaDB 1.0.0-preview.2, 1.0.0-preview.3, 1.0.0-preview.3.post1 and 1.0.0-preview.4, after their trials on a k3d volume: two runs with the same outcome, from Chroma 1.5.9 the same as with 1.0.0-preview.3.post1. The README, the examples of the CRD and the end-to-end tests use the latest release.
Laurianti
force-pushed
the
feat/vecturadb-post-releases
branch
from
November 3, 2026 17:35
e5f09a6 to
57de7ab
Compare
ambergrove
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The operator refused an update to VecturaDB 1.0.0-preview.5, the latest release of VecturaDB: no passage of its table led there. It also refused the post-releases of the previews, like 1.0.0-preview.3.post1: its pattern took only
x.y.zandx.y.z-preview.N.x.y.z-preview.N.postM, as VecturaDB tags them. The order is the one of SemVer 2.0:1.0.0-preview.3<1.0.0-preview.3.post1<1.0.0-preview.4<1.0.0. Post-releases compare by number, as in PEP 440. A post-release of a release, or one without its number, is refused, by the API too.1.0.0-preview.5: from Chroma 1.5.9 and from VecturaDB1.0.0-preview.2,1.0.0-preview.3,1.0.0-preview.3.post1and1.0.0-preview.4. To1.0.0-preview.3.post1: from Chroma 1.5.9 and from VecturaDB1.0.0-preview.2and1.0.0-preview.3.The trials to
1.0.0-preview.5ran on 3/11/2026 on a k3d local-path volume, on an Azure Standard_D8ds_v7 VM, with the Pods as the operator runs them, twice:1.0.0-preview.3.post1, in the 41 checks of these cases.1.0.0-preview.5. In 16 further starts, 8 of1.0.0-preview.5and 8 of1.0.0-preview.4, requests to the IP of the Pod were never refused, and the Service answered within 1.71 s of Ready, with no restart. A client of a new Pod can see the same.The images of
1.0.0-preview.3.post1and1.0.0-preview.5startvecturadb. The operator sets neither the command nor the arguments of a single node, so the image starts as it is.Tests rerun at the head of this PR, on the same VM: the unit tests, 315 of 315, and on k3d the end-to-end tests of VecturaDB and of the image tags, 9 of 9, in two runs. The manifest and the reference of the chart are those the scripts generate. The rest is left to the CI.