Repository navigation
docs(web): add the changelog entry for 0.1.4 - #50
Conversation
The entry covers the four fixes in the release: full topK on pgvector and Supabase, rejected malformed filters and delete selectors, batches that stop after a failure, and the Vectorize default-namespace query. It tells Supabase users to re-run sql/supabase.sql and names the new @upstash/vector peer floor. The date is the npm publish date in Bangkok time.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
commit: |
Background
vecstore-sdk0.1.4 was published to npm on 2026-10-04 (Bangkok time) from #45. The release guide asks for a site changelog entry for every publish, and 0.1.4 has none yet.Summary
apps/web/content/changelog/v0.1.4.mdx: the four fixes in the release, each in its own section, and the smaller changes in a list.sql/supabase.sql, and names the new@upstash/vectorpeer floor of 1.2.1.dateis the npm publish date in Bangkok time, like the earlier entries.The docs site deployed when 0.1.4 was published, before this entry existed. After this merges, the entry goes live on a manual redeploy or with the next release.
Verification
bun run checkandbun run typecheckexit 0. The typecheck compiles the changelog collection, so it validates the frontmatter.bun x turbo run build --filter=webbuilds the site and generates/changelog/v0.1.4.Checklist
vecstore-sdk(runbun run changesetin the project root). Not needed, because nothing underpackages/changes.Summary by CodeRabbit
Bug Fixes
Improvements