Repository navigation
chore(release): version packages - #90
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
November 14, 2026 16:24
251717f to
a5164c6
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 14, 2026 18:19
a5164c6 to
e03e6b6
Compare
PunGrumpy
enabled auto-merge (squash)
November 14, 2026 18:23
commit: |
4 tasks
PunGrumpy
added a commit
that referenced
this pull request
Nov 14, 2026
The version pull request (#90) computed 0.2.0 for the first minor release on 0.1.x. That version was published and unpublished on 2026-09-10, and npm never accepts a version twice, so the Release job failed at publish. 0.3.0 has never been published. The changelog entries stay the same.
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
vecstore-sdk@0.2.0
Minor Changes
scan, which pages through every record in an index's namespace on all seven adapters:const page = await index.scan({ cursor, limit, includeVector })returns up tolimitrecords and acursorfor the next call,undefinedonce the scan is done. Records come back with the ids you wrote, including on Qdrant, Vectorize, and Upstash, where the provider stores a hashed or prefixed id. A page can be short or empty whilecursoris set. Pinecone supports it on serverless indexes only. Supabase users re-runsql/supabase.sqlto installvecstore_scan.VectorIndexand theQdrantClientLike,PineconeIndexLike,UpstashIndexLike, andRedisClientLiketypes gain a required member, so code that implements them by hand needs the new method.unwrap, which returns the value of a successfulResultand throws anErrorfor a failed one. The error's message names the provider and the kind, such asqdrant connection: fetch failed, and itscauseis the originalVecstoreError. Code that only wants to stop on a failure no longer writesthrow new Error(result.error.message), which dropped both.Patch Changes
fetchreturnsvector: []unless you pass{ includeVector: true }, and it returns the sameVectorRecordtype thatupserttakes, so fetching a record, changing its metadata, and upserting it typechecked. On Redis that call returnedokand stored a document with an empty vector, which the search index leaves out of every query; the other adapters passed the empty vector on to the provider. Every adapter'supsertnow returnsinvalid_argumentand writes nothing when a vector is empty, holdsNaNor an infinite value, or has a different length from the first record in the call.queryreturnsinvalid_argumentfor an empty or non-finite query vector.upserton Qdrant, Upstash Vector, and Cloudflare Vectorize. These adapters converted every record into the provider's request shape before sending the first batch, so the converted copy of the whole input stayed alive until the last batch finished. They now convert each batch as it is sent, as the pgvector, Supabase, and Pinecone adapters already did. With 5,000 records of 1,536 dimensions, the memory still reachable while requests ran dropped from about 140 MB to about 1 MB on Vectorize and from about 60 MB to under 10 MB on Qdrant and Upstash. Requests and their order are unchanged.