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]

Patch Changes

• #883 9320326 Thanks @omeraplak! - feat: add authNext and deprecate legacy auth

  Add a new authNext policy that splits routes into public, console, and user access. All routes are protected by default; use publicRoutes to opt out.

  AuthNext example:

  import { jwtAuth } from "@voltagent/server-core";
  import { honoServer } from "@voltagent/server-hono";
  
  const server = honoServer({
    authNext: {
      provider: jwtAuth({ secret: process.env.JWT_SECRET! }),
      publicRoutes: ["GET /health"],
    },
  });

  Behavior summary:

  • When authNext is set, all routes are private by default.
  • Console endpoints (agents, workflows, tools, docs, observability, updates) require a Console Access Key.
  • Execution endpoints require a user token (JWT).

  Console access uses VOLTAGENT_CONSOLE_ACCESS_KEY:

  VOLTAGENT_CONSOLE_ACCESS_KEY=your-console-key

  curl http://localhost:3141/agents \
    -H "x-console-access-key: your-console-key"

  Legacy auth remains supported but is deprecated. Use authNext for new integrations.

@voltagent/[email protected]

Patch Changes

• #883 9320326 Thanks @omeraplak! - feat: add authNext and deprecate legacy auth

  Add a new authNext policy that splits routes into public, console, and user access. All routes are protected by default; use publicRoutes to opt out.

  AuthNext example:

  import { jwtAuth } from "@voltagent/server-core";
  import { honoServer } from "@voltagent/server-hono";
  
  const server = honoServer({
    authNext: {
      provider: jwtAuth({ secret: process.env.JWT_SECRET! }),
      publicRoutes: ["GET /health"],
    },
  });

  Behavior summary:

  • When authNext is set, all routes are private by default.
  • Console endpoints (agents, workflows, tools, docs, observability, updates) require a Console Access Key.
  • Execution endpoints require a user token (JWT).

  Console access uses VOLTAGENT_CONSOLE_ACCESS_KEY:

  VOLTAGENT_CONSOLE_ACCESS_KEY=your-console-key

  curl http://localhost:3141/agents \
    -H "x-console-access-key: your-console-key"

  Legacy auth remains supported but is deprecated. Use authNext for new integrations.

• Updated dependencies [9320326]:

  • @voltagent/[email protected]

---

Summary by cubic

Publish patch releases for @voltagent/server-core and @voltagent/server-hono introducing the new authNext policy and deprecating legacy auth. Example apps are updated to use the latest server-hono.

• New Features

  • Add authNext with public, console, and user access tiers.
  • Routes are private by default; set publicRoutes to opt out.
  • Console endpoints require x-console-access-key; execution endpoints require a user JWT. Legacy auth remains but is deprecated.

• Dependencies

  • Bump @voltagent/server-core to 1.0.36 and @voltagent/server-hono to 1.2.11.
  • Update all example apps to ^1.2.11 of server-hono.
  • Refresh pnpm-lock.yaml and remove the consumed changeset file.

^{Written for commit 2148ca0. Summary will update automatically on new commits.}

[cubic-dev-ai]

No issues found across 68 files

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	2148ca0
Status:	✅  Deploy successful!
Preview URL:	https://ca6397d0.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs