What changed

Vanna released 2.0.0rc1 as a prerelease rewrite of its text-to-SQL library. Identity and permissions flow into tools, row-level security and audit logs; the new framework adds schema-aware tools, a drop-in streaming web component, FastAPI and Flask servers, lifecycle hooks, middleware, evaluation and vector-store-backed memory.

Why it matters

Analytics agents need authorization to survive the full path from user identity to generated query and returned rows. Vanna's rewrite makes that path inspectable instead of treating text-to-SQL as a model-only problem, while also making migration and server behavior a new compatibility boundary.

What to do

Evaluate the release candidate on a masked database. Give two test users different row and tool permissions, ask equivalent questions, inject an unauthorized table reference and inspect SQL, returned rows, audit logs, rate limits and streamed UI output before considering migration from 0.x.

Caveat

This is an explicitly marked release candidate and a full architectural rewrite, not general availability or an independent proof of row-level security. Existing integrations may require a legacy adapter or full rewrite, and real authorization still depends on correct database policy, identity propagation and server configuration.