Repository navigation
2.22.1 - #173
Merged
Merged
2.22.1#173
Conversation
ambergrove
approved these changes
Nov 16, 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.
Version 2.22.1 in the four packages: the same code as 2.22.0, with the fix of #171,
chromadotnettaking VecturaDB 1.0.0-preview.10.post1 as the version it was tested with.Tested: the packages built from this commit as the CI builds them have the same content as the ones of 2.22.0 on nuget.org, but the version, the commit and that version of VecturaDB in the command. The command from the package made a backup, a restore and a verification against VecturaDB 1.0.0-preview.10.post1 and Chroma 1.5.9 with no warning, and against VecturaDB 1.0.0-preview.9 with the warning.