chore: version packages - #5
Merged
Merged
Conversation
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 master, this PR will be updated.
Releases
vec-cache@1.1.0
Minor Changes
getOrCreatenow checks an explicitdimensionsrequest against whatembedactually returns, and passes the requested width to the callback as
request.dimensions. A callback that ignores it and returns another widththrows
EMBED_DIMENSION_MISMATCHbefore anything is written, instead ofstoring a row keyed as the requested width and stored at another — which made
every later identical call demote the row and pay for the same embedding
again.
getOrCreate'smaxEmbedBatchSizeoption: a cap on how many texts go toembedin one call, so a cold cache over a large corpus no longer hands thecallback more inputs than the provider accepts. Sub-batches run in order and
each is cached as it succeeds — a later failure leaves the completed ones
cached and throws — and
report.embedCallCountis the number of callsactually made. Omitting it keeps the previous behavior: one call for every
unique miss.
Patch Changes
busyTimeoutMswhile the database is being opened. It was applied onlyafter the header probe, the migration reads and the WAL switch, so until then
the driver's own 5 s default was in force and a larger configured timeout was
silently capped — losing the race against another process checkpointing its
WAL on
close().