Conversation
Deploying voltagent with
|
| Latest commit: |
83286b2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d4a20be9.voltagent.pages.dev |
| Branch Preview URL: | https://changeset-release-main.voltagent.pages.dev |
This comment has been minimized.
This comment has been minimized.
📝 WalkthroughWalkthroughThis PR releases version 2.1.1 of Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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 |
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
@voltagent/[email protected]
Patch Changes
#1038
9757223Thanks @omeraplak! - fix: deduplicate conversation step rows before Supabase upsertsaveConversationStepsnow deduplicates rows byidin a batch before calling Supabaseupsert.This prevents Postgres errors like
ON CONFLICT DO UPDATE command cannot affect row a second timewhen multiple step records with the sameidare present in one persistence batch, while preserving current last-write-wins behavior.Summary by cubic
Publish @voltagent/supabase v2.1.1 with a fix to prevent Postgres ON CONFLICT errors during batch upserts. Example app dependency and lockfile updated to the new version.
Bug Fixes
Dependencies
Written for commit 83286b2. Summary will update on new commits.
Summary by CodeRabbit
Bug Fixes
Chores