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/[email protected]

Major Changes

• #674 5aa84b5 Thanks @omeraplak! - feat: initial release

Patch Changes

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

@voltagent/[email protected]

Major Changes

• #674 5aa84b5 Thanks @omeraplak! - feat: initial release

Patch Changes

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

@voltagent/[email protected]

Major Changes

• #674 5aa84b5 Thanks @omeraplak! - feat: add dataset/evals/experiments functions

Patch Changes

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

@voltagent/[email protected]

Patch Changes

• #674 5aa84b5 Thanks @omeraplak! - feat: add eval commands

• Updated dependencies [5aa84b5, 5aa84b5]:

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

@voltagent/[email protected]

Patch Changes

• #674 5aa84b5 Thanks @omeraplak! - feat: add live evals

• #674 5aa84b5 Thanks @omeraplak! - ## What Changed

  Removed automatic message pruning functionality from all storage adapters (PostgreSQL, Supabase, LibSQL, and InMemory). Previously, messages were automatically deleted when the count exceeded storageLimit (default: 100 messages per conversation).

  Why This Change

  Users reported unexpected data loss when their conversation history exceeded the storage limit. Many users expect their conversation history to be preserved indefinitely rather than automatically deleted. This change gives users full control over their data retention policies.

  Migration Guide

  Before

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      storageLimit: 200, // Messages auto-deleted after 200
    }),
  });

  After

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      // No storageLimit - all messages preserved
    }),
  });

  If You Need Message Cleanup

  Implement your own cleanup logic using the clearMessages() method:

  // Clear all messages for a conversation
  await memory.clearMessages(userId, conversationId);
  
  // Clear all messages for a user
  await memory.clearMessages(userId);

  Affected Packages

  • @voltagent/core - Removed storageLimit from types
  • @voltagent/postgres - Removed from PostgreSQL adapter
  • @voltagent/supabase - Removed from Supabase adapter
  • @voltagent/libsql - Removed from LibSQL adapter

  Impact

  • ✅ No more unexpected data loss
  • ✅ Users have full control over message retention
  • ⚠️ Databases may grow larger over time (consider implementing manual cleanup)
  • ⚠️ Breaking change: storageLimit parameter no longer accepted

@voltagent/[email protected]

Patch Changes

• #674 5aa84b5 Thanks @omeraplak! - ## What Changed

  Removed automatic message pruning functionality from all storage adapters (PostgreSQL, Supabase, LibSQL, and InMemory). Previously, messages were automatically deleted when the count exceeded storageLimit (default: 100 messages per conversation).

  Why This Change

  Users reported unexpected data loss when their conversation history exceeded the storage limit. Many users expect their conversation history to be preserved indefinitely rather than automatically deleted. This change gives users full control over their data retention policies.

  Migration Guide

  Before

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      storageLimit: 200, // Messages auto-deleted after 200
    }),
  });

  After

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      // No storageLimit - all messages preserved
    }),
  });

  If You Need Message Cleanup

  Implement your own cleanup logic using the clearMessages() method:

  // Clear all messages for a conversation
  await memory.clearMessages(userId, conversationId);
  
  // Clear all messages for a user
  await memory.clearMessages(userId);

  Affected Packages

  • @voltagent/core - Removed storageLimit from types
  • @voltagent/postgres - Removed from PostgreSQL adapter
  • @voltagent/supabase - Removed from Supabase adapter
  • @voltagent/libsql - Removed from LibSQL adapter

  Impact

  • ✅ No more unexpected data loss
  • ✅ Users have full control over message retention
  • ⚠️ Databases may grow larger over time (consider implementing manual cleanup)
  • ⚠️ Breaking change: storageLimit parameter no longer accepted

@voltagent/[email protected]

Patch Changes

• #674 5aa84b5 Thanks @omeraplak! - ## What Changed

  Removed automatic message pruning functionality from all storage adapters (PostgreSQL, Supabase, LibSQL, and InMemory). Previously, messages were automatically deleted when the count exceeded storageLimit (default: 100 messages per conversation).

  Why This Change

  Users reported unexpected data loss when their conversation history exceeded the storage limit. Many users expect their conversation history to be preserved indefinitely rather than automatically deleted. This change gives users full control over their data retention policies.

  Migration Guide

  Before

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      storageLimit: 200, // Messages auto-deleted after 200
    }),
  });

  After

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      // No storageLimit - all messages preserved
    }),
  });

  If You Need Message Cleanup

  Implement your own cleanup logic using the clearMessages() method:

  // Clear all messages for a conversation
  await memory.clearMessages(userId, conversationId);
  
  // Clear all messages for a user
  await memory.clearMessages(userId);

  Affected Packages

  • @voltagent/core - Removed storageLimit from types
  • @voltagent/postgres - Removed from PostgreSQL adapter
  • @voltagent/supabase - Removed from Supabase adapter
  • @voltagent/libsql - Removed from LibSQL adapter

  Impact

  • ✅ No more unexpected data loss
  • ✅ Users have full control over message retention
  • ⚠️ Databases may grow larger over time (consider implementing manual cleanup)
  • ⚠️ Breaking change: storageLimit parameter no longer accepted

@voltagent/[email protected]

Patch Changes

• #674 5aa84b5 Thanks @omeraplak! - ## What Changed

  Removed automatic message pruning functionality from all storage adapters (PostgreSQL, Supabase, LibSQL, and InMemory). Previously, messages were automatically deleted when the count exceeded storageLimit (default: 100 messages per conversation).

  Why This Change

  Users reported unexpected data loss when their conversation history exceeded the storage limit. Many users expect their conversation history to be preserved indefinitely rather than automatically deleted. This change gives users full control over their data retention policies.

  Migration Guide

  Before

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      storageLimit: 200, // Messages auto-deleted after 200
    }),
  });

  After

  const memory = new Memory({
    storage: new PostgreSQLMemoryAdapter({
      connection: process.env.DATABASE_URL,
      // No storageLimit - all messages preserved
    }),
  });

  If You Need Message Cleanup

  Implement your own cleanup logic using the clearMessages() method:

  // Clear all messages for a conversation
  await memory.clearMessages(userId, conversationId);
  
  // Clear all messages for a user
  await memory.clearMessages(userId);

  Affected Packages

  • @voltagent/core - Removed storageLimit from types
  • @voltagent/postgres - Removed from PostgreSQL adapter
  • @voltagent/supabase - Removed from Supabase adapter
  • @voltagent/libsql - Removed from LibSQL adapter

  Impact

  • ✅ No more unexpected data loss
  • ✅ Users have full control over message retention
  • ⚠️ Databases may grow larger over time (consider implementing manual cleanup)
  • ⚠️ Breaking change: storageLimit parameter no longer accepted

[email protected]

Patch Changes

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

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	5816525
Status:	✅  Deploy successful!
Preview URL:	https://9259bbbb.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs