[email protected]

Patch Changes

• 59b4a3e Thanks @omeraplak! - feat: add VoltAgent v1 support

@voltagent/[email protected]

@voltagent/[email protected]

@voltagent/[email protected]

@voltagent/[email protected]

@voltagent/[email protected]

Major Changes

• a2b492e Thanks @omeraplak! - # Supabase 1.x — Memory Adapter

  Supabase storage now implements the Memory V2 adapter pattern.

  Full migration guide: Migration Guide

  Migrate

  Before (0.1.x):

  import { SupabaseMemory } from "@voltagent/supabase";
  
  const agent = new Agent({
    // ...
    memory: new SupabaseMemory({ url: process.env.SUPABASE_URL!, key: process.env.SUPABASE_KEY! }),
  });

  After (1.x):

  import { Memory } from "@voltagent/core";
  import { SupabaseMemoryAdapter } from "@voltagent/supabase";
  
  const agent = new Agent({
    // ...
    memory: new Memory({
      storage: new SupabaseMemoryAdapter({
        url: process.env.SUPABASE_URL!,
        key: process.env.SUPABASE_KEY!,
      }),
    }),
  });

Patch Changes

• c2a6ae1 Thanks @omeraplak! - fix: @voltagent/logger dependency

@voltagent/[email protected]

Patch Changes

• Updated dependencies [63d4787]:
  • @voltagent/[email protected]
  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• 3177a60 Thanks @omeraplak! - fix: version bump

• Updated dependencies [3177a60]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• c27b260 Thanks @omeraplak! - fix: zod dependency moved from dependencies to devDependencies

• Updated dependencies [c27b260]:

  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• #545 5d7c8e7 Thanks @omeraplak! - fix: resolve EADDRINUSE error on server startup by fixing race condition in port availability check - #544

  Fixed a critical issue where users would encounter "EADDRINUSE: address already in use" errors when starting VoltAgent servers. The problem was caused by a race condition in the port availability check where the test server wasn't fully closed before the actual server tried to bind to the same port.

  What was happening

  When checking if a port was available, the port manager would:

  1. Create a test server and bind to the port
  2. On successful binding, immediately close the server
  3. Return true indicating the port was available
  4. But the test server wasn't fully closed yet when serve() tried to bind to the same port

  The fix

  Modified the port availability check in port-manager.ts to:

  • Wait for the server's close callback before returning
  • Add a small delay (50ms) to ensure the OS has fully released the port
  • This prevents the race condition between test server closure and actual server startup

  Changes

  • port-manager.ts: Fixed race condition by properly waiting for test server to close
  • hono-server-provider.ts: Added proper error handling for server startup failures

  This ensures reliable server startup without port conflicts.

• #546 f12f344 Thanks @omeraplak! - chore: align Zod to ^3.25.76 and fix type mismatch with AI SDK

  We aligned Zod versions across packages to ^3.25.76 to match AI SDK peer ranges and avoid multiple Zod instances at runtime.

  Why this matters

  • Fixes TypeScript narrowing issues in workflows when consuming @voltagent/core from npm with a different Zod instance (e.g., ai packages pulling newer Zod).
  • Prevents errors like "Spread types may only be created from object types" where data failed to narrow because z.ZodTypeAny checks saw different Zod identities.

  What changed

  • @voltagent/server-core, @voltagent/server-hono: dependencies.zod → ^3.25.76.
  • @voltagent/docs-mcp, @voltagent/core: devDependencies.zod → ^3.25.76.
  • Examples and templates updated to use ^3.25.76 for consistency (non-publishable).

  Notes for consumers

  • Ensure a single Zod version is installed (consider a workspace override to pin Zod to 3.25.76).
  • This improves compatibility with [email protected] packages that require zod@^3.25.76 || ^4.

• Updated dependencies [5d7c8e7, f12f344]:

  • @voltagent/[email protected]
  • @voltagent/[email protected]

@voltagent/[email protected]

Major Changes

• a2b492e Thanks @omeraplak! - # Server Hono 1.x — pluggable HTTP server

  Core no longer embeds an HTTP server. Use the Hono provider.

  Full migration guide: Migration Guide

  Basic setup

  import { VoltAgent } from "@voltagent/core";
  import { honoServer } from "@voltagent/server-hono";
  
  new VoltAgent({
    agents: { agent },
    server: honoServer({ port: 3141, enableSwaggerUI: true }),
  });

  Custom routes and auth

  import { honoServer, jwtAuth } from "@voltagent/server-hono";
  
  new VoltAgent({
    agents: { agent },
    server: honoServer({
      configureApp: (app) => {
        app.get("/api/health", (c) => c.json({ status: "ok" }));
      },
      auth: jwtAuth({
        secret: process.env.JWT_SECRET!,
        publicRoutes: ["/health", "/metrics"],
      }),
    }),
  });

Patch Changes

• Updated dependencies [a2b492e, a2b492e]:
  • @voltagent/[email protected]
  • @voltagent/[email protected]

@voltagent/[email protected]

Patch Changes

• 3177a60 Thanks @omeraplak! - fix: version bump