Support for the Qdrant v1.19.0 API across @qdrant/qdrant-js, @qdrant/js-client-rest and @qdrant/js-client-grpc.
⚠️ Breaking changes
The REST client dropped search, searchBatch, searchPointGroups, recommend, recommendBatch, recommend_batch, recommendPointGroups, discoverPoints and discoverBatchPoints, following Qdrant dropping the corresponding endpoints from its OpenAPI spec. Use query, queryBatch and queryGroups instead:
| Removed | Replacement |
|---|---|
search
| query
|
searchBatch
| queryBatch
|
searchPointGroups
| queryGroups
|
recommend
| query with a recommend query
|
recommendBatch
| queryBatch with recommend queries
|
recommendPointGroups
| queryGroups with a recommend query
|
discoverPoints
| query with a discover or context query
|
discoverBatchPoints
| queryBatch with discover or context queries
|
Note that query and friends return {points: [...]} rather than a bare array.
The request types that came with them are gone from Schemas as well: SearchRequest, SearchRequestBatch, SearchGroupsRequest, RecommendRequest, RecommendRequestBatch, RecommendGroupsRequest, DiscoverRequest, DiscoverRequestBatch, RecommendExample, ContextExamplePair, NamedVector, NamedSparseVector, NamedVectorStruct and UsingVector.
The gRPC client still exposes the corresponding RPCs — Search, SearchBatch, SearchGroups, Recommend, RecommendBatch, RecommendGroups, Discover and DiscoverBatch are marked deprecated upstream but remain functional. Use Query, QueryBatch and QueryGroups instead.
New in the REST client
- Added
getQuotasandupdateQuotasfor the cluster-wide quota API. - Added
payload(payload storage params) andmetadataparameters tocreateCollectionandrecreateCollection. max_disk_usage_percentmoved offstrict_mode_config— it is now a cluster-wide setting onupdateQuotas, alongsidemax_resident_memory_percentandrelease_margin_percent.
New in the gRPC client
StrictModeConfig.max_disk_usage_percentis gone, superseded by the cluster-wide quota config, andmax_resident_memory_percentis deprecated with removal planned for 1.21. The quota API itself is REST-only for now.
What's Changed
- ci: update GitHub Actions to Node 24 before June 2 deadline by @estebany-qd in #135
- ci: update third-party actions to node 24 by @estebany-qd in #136
- chore: add Dependabot configuration by @andres-qd in #137
- chore: update dependencies and resolve security alerts by @Anush008 in #150
- Bump undici from 6.27.0 to 7.29.0 by @dependabot in #159
- v1.19 by @IvanPleshkov in #164
- Fix prepublish for Node 24 by @IvanPleshkov in #167
- Pass the npm token the way setup-node expects by @IvanPleshkov in #168
- ci: publish to npm via trusted publishing (OIDC) by @IvanPleshkov in #169
Full Changelog: v1.18.0...v1.19.0