Skip to content

chore(release): version packages - #90

Merged
PunGrumpy merged 1 commit into
mainfrom
changeset-release/main
Nov 14, 2026
Merged

PunGrumpy merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

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

  • c1fd3a5: Add 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 to limit records and a cursor for the next call, undefined once 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 while cursor is set. Pinecone supports it on serverless indexes only. Supabase users re-run sql/supabase.sql to install vecstore_scan. VectorIndex and the QdrantClientLike, PineconeIndexLike, UpstashIndexLike, and RedisClientLike types gain a required member, so code that implements them by hand needs the new method.
  • 7f1c720: Add unwrap, which returns the value of a successful Result and throws an Error for a failed one. The error's message names the provider and the kind, such as qdrant connection: fetch failed, and its cause is the original VecstoreError. Code that only wants to stop on a failure no longer writes throw new Error(result.error.message), which dropped both.

Patch Changes

  • 9dd2fe3: Reject a vector that cannot be stored before any adapter writes it. fetch returns vector: [] unless you pass { includeVector: true }, and it returns the same VectorRecord type that upsert takes, so fetching a record, changing its metadata, and upserting it typechecked. On Redis that call returned ok and 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's upsert now returns invalid_argument and writes nothing when a vector is empty, holds NaN or an infinite value, or has a different length from the first record in the call. query returns invalid_argument for an empty or non-finite query vector.
  • 3df1182: Hold less memory during a large upsert on 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.

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f1a9b9eb-1b84-407c-9eab-dea9b26c85b2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 251717f to a5164c6 Compare November 14, 2026 16:24
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a5164c6 to e03e6b6 Compare November 14, 2026 18:19
@PunGrumpy
PunGrumpy enabled auto-merge (squash) November 14, 2026 18:23
@pkg-pr-new

pkg-pr-new Bot commented Nov 14, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/vecstore-sdk@90

commit: e03e6b6

@PunGrumpy
PunGrumpy merged commit d415e1d into main Nov 14, 2026
11 checks passed
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant