Skip to content

VecturaDB 1.0.0-preview.5: the passages to the latest release, and the post-releases of the previews - #19

Merged
Laurianti merged 4 commits into
mainfrom
feat/vecturadb-post-releases
Nov 3, 2026
Merged

Laurianti merged 4 commits into
mainfrom
feat/vecturadb-post-releases

Conversation

@Laurianti

@Laurianti Laurianti commented Oct 28, 2026 •

Copy link
Copy Markdown
Member

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.z and x.y.z-preview.N.

  • Versions. A post-release of a preview, 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.
  • Passages. Eight rows of the table. To 1.0.0-preview.5: 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. To 1.0.0-preview.3.post1: from Chroma 1.5.9 and from VecturaDB 1.0.0-preview.2 and 1.0.0-preview.3.
  • Docs and tests. The README, the examples of the CRD and the end-to-end tests of VecturaDB use the latest release. The notes of the next release say it.

The trials to 1.0.0-preview.5 ran 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:

  • From Chroma 1.5.9: the 200 dense records intact, with the same ids and results; BM25 and sparse vectors written and searched; the same results as with 1.0.0-preview.3.post1, in the 41 checks of these cases.
  • From each VecturaDB, also on data of Chroma 1.5.9: the records intact, the BM25 and sparse searches with the same results, new records written and found.
  • Every start of a server became Ready, and the two runs gave the same results on the data.
  • The first request through the Service right after Ready was refused on 6 of the 18 starts of 1.0.0-preview.5. In 16 further starts, 8 of 1.0.0-preview.5 and 8 of 1.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.post1 and 1.0.0-preview.5 start vecturadb. 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.

@Laurianti
Laurianti requested a review from a team as a code owner October 28, 2026 22:19
… 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
Laurianti force-pushed the feat/vecturadb-post-releases branch from e5f09a6 to 57de7ab Compare November 3, 2026 17:35
@Laurianti Laurianti changed the title VecturaDB 1.0.0-preview.3.post1: post-releases of the previews, and their passages VecturaDB 1.0.0-preview.5: the passages to the latest release, and the post-releases of the previews Nov 3, 2026
@Laurianti
Laurianti merged commit 09e54b4 into main Nov 3, 2026
4 checks passed
@Laurianti
Laurianti deleted the feat/vecturadb-post-releases branch November 3, 2026 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants