Agno 3.0.8 fixes a bulk upsert overwrite bug

Agno's SqliteDb and AsyncSqliteDb adapters let one user's data overwrite another's through the bulk upsert path, per the project's 3.0.8 release notes. Calling upsert_sessions() with a batch that included someone else's session_id would reassign that row and replace its contents.

Any app calling bulk upsert with session IDs pulled from user input or a shared queue was exposed. A batch didn't need special permissions to hit another tenant's row, just the right ID in the list.

Agno had already built a single-row owner check for SQLite, but it only ran on single-row writes. The bulk path skipped it entirely. Version 3.0.8 applies the same check to every row in a bulk upsert.

Rows that fail the check now get dropped from the batch instead of overwriting anything. They're also omitted from the returned list, matching how the Postgres adapter already worked. The release separately stops the SQLite adapters from double-encoding session JSON.

The fix is a patch version, so the upgrade should be low-friction. The release notes don't say whether other bulk operations in the SQLite adapters still skip per-row checks that the single-row path enforces. That gap tends to stay invisible until someone runs a batch large enough to include an ID nobody expected.