Build on ChromaDotNet.Client 2.11.0 as 0.4.2

Directory.Packages.props

@@ -9,8 +9,8 @@
   <ItemGroup Label="MEVD">
     <PackageVersion Include="Microsoft.Extensions.VectorData.Abstractions" Version="10.10.0" />
     <PackageVersion Include="Microsoft.Extensions.VectorData.ConformanceTests" Version="10.10.0" />
-    <PackageVersion Include="ChromaDotNet.Client" Version="2.10.2" />
-    <PackageVersion Include="ChromaDotNet.Client.DependencyInjection" Version="2.10.2" />
+    <PackageVersion Include="ChromaDotNet.Client" Version="2.11.0" />
+    <PackageVersion Include="ChromaDotNet.Client.DependencyInjection" Version="2.11.0" />
   </ItemGroup>
 
   <ItemGroup Label="Build">

src/ChromaDB.VectorData/ChromaDB.VectorData.csproj

@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <VersionPrefix>0.4.1</VersionPrefix>
+    <VersionPrefix>0.4.2</VersionPrefix>
     <AssemblyName>ChromaDB.VectorData</AssemblyName>
     <PackageId>ChromaDotNet.VectorData</PackageId>
     <RootNamespace>$(AssemblyName)</RootNamespace>
@@ -11,7 +11,7 @@
     <Title>Chroma provider for Microsoft.Extensions.VectorData</Title>
     <Description>Microsoft.Extensions.VectorData provider for Chroma and Chroma Cloud, built on ChromaDotNet.Client. Community project, not affiliated with Chroma.</Description>
     <PackageTags>chroma chromadb chroma-cloud vector-database vectordata ai</PackageTags>
-    <PackageReleaseNotes>0.4.1: This version needs ChromaDotNet.Client 2.10.2. On Chroma Cloud, a filter on the keys with a large top, like GetAsync(r => r.Key == "a", top: 1000), no longer goes over the quota of 300 records per request: the client asks for at most as many records as there are keys. All the releases: https://github.com/ChromaDotNet/ChromaDB.VectorData/releases</PackageReleaseNotes>
+    <PackageReleaseNotes>0.4.2: This version needs ChromaDotNet.Client 2.11.0. The README says that array and list properties, like the namespaces of the TextSearchStore of Semantic Kernel, need Chroma 1.5.0 or later. All the releases: https://github.com/ChromaDotNet/ChromaDB.VectorData/releases</PackageReleaseNotes>
   </PropertyGroup>
 
   <ItemGroup>

src/ChromaDB.VectorData/README.md

@@ -158,7 +158,7 @@ A single Chroma server has neither the Search API nor sparse vector indexes: the
 - `GetAsync` with a filter does not support ordering.
 - Comparisons work on numbers only. A negated comparison, like `!(r.Rating > 3)`, is not supported on a nullable property: Chroma would leave out the records where the property is null.
 - A `DateTime` filter finds the same ticks with the same `Kind`.
-- Array properties need Chroma 1.5.0 or later.
+- Array and list properties, like the namespaces of the `TextSearchStore` of Semantic Kernel, need Chroma 1.5.0 or later.
 - Hybrid search needs Chroma Cloud.
 - On Chroma Cloud, a vector search returns at most 300 results, `Skip` included, the default quota of Chroma Cloud: beyond that, Chroma Cloud answers with a quota error.
 - Only one property can be the document. With more than one full-text indexed string property, none is.