ci(changesets): version packages

[voltagent-bot]

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/core@0.1.83

Patch Changes

• Updated dependencies [5968cef]:
  • @voltagent/internal@0.0.9

@voltagent/internal@0.0.9

Patch Changes

• 5968cef Thanks @omeraplak! - chore: remove console.warn from deepClone function

  Removed the console.warn statement from the deepClone function's error handling. Since we require Node.js 17+ where structuredClone is always available, this warning is unnecessary and can clutter logs in development environments.

  What Changed

  • Removed console.warn("Failed to deep clone object, using shallow clone", { error }); from the catch block
  • Kept the fallback logic intact for edge cases
  • Maintained the development-only condition check even though the warning is removed

  This change reduces unnecessary console output while maintaining the same fallback behavior for shallow cloning when structuredClone fails.

@voltagent/logger@0.1.4

Patch Changes

• Updated dependencies [5968cef]:
  • @voltagent/internal@0.0.9

@voltagent/supabase@0.1.20

Patch Changes

• #496 0dcc675 Thanks @omeraplak! - fix: resolve SupabaseClient ESM import error

  Fixed an issue where SupabaseClient was not available as a runtime export in the ESM build of @supabase/supabase-js v2.54.0. The type is exported in TypeScript definitions but not in the actual ESM runtime.

  What Changed

  • Changed SupabaseClient to a type-only import using import { type SupabaseClient }
  • Replaced P.instanceOf(SupabaseClient) pattern matching with P.not(P.nullish) since the class is not available at runtime
  • Added type assertion to maintain TypeScript type safety

  Before

  import { SupabaseClient, createClient } from "@supabase/supabase-js";
  // ...
  .with({ client: P.instanceOf(SupabaseClient) }, (o) => o.client)

  After

  import { createClient, type SupabaseClient } from "@supabase/supabase-js";
  // ...
  .with({ client: P.not(P.nullish) }, (o) => o.client as SupabaseClient)

  This ensures compatibility with both CommonJS and ESM module systems while maintaining full type safety.

• Updated dependencies [5968cef]:

  • @voltagent/internal@0.0.9
  • @voltagent/logger@0.1.4

@voltagent/vercel-ui@0.1.10

Patch Changes

• Updated dependencies [5968cef]:
  • @voltagent/internal@0.0.9

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	0eaf43c
Status:	✅  Deploy successful!
Preview URL:	https://a409544b.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs

[ghost]

📝 Documentation Analysis

All docs are up to date! 🎉

---

✅ Latest commit analyzed: 0eaf43c | Powered by Joggr