Repository navigation
VecturaDB 1.0.0-preview.10.post1 in the CI - #171
Merged
Merged
Conversation
ambergrove
approved these changes
Nov 16, 2026
Merged
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.
VecturaDB 1.0.0-preview.10.post1 in the CI in place of 1.0.0-preview.9, and as the version that
chromadotnetwas tested with, so that it does not warn on it.Tested: the suite against VecturaDB 1.0.0-preview.10.post1, with the restore into Chroma 1.5.9 and back: 3024 tests, 3012 passed, 12 skipped, 0 failed, the same tests passed and skipped as against 1.0.0-preview.9.