chore: daily sync of plugin metadata and READMEs [automated]

Author: github-actions[bot]

plugins/advanced-alchemy.yml

@@ -15,8 +15,8 @@ maintainers:
 compatibility:
   litestar: '>=2.0.0'
 icon: advanced-alchemy.png
-stars: 774
-monthly_downloads: 413071
+stars: 775
+monthly_downloads: 440702
 latest_version: 1.11.0
 updated_at: '2026-05-31T18:14:26'
 created_at: '2023-09-17T17:39:42'

plugins/litestar-asyncpg.yml

@@ -16,7 +16,7 @@ compatibility:
   litestar: '>=2.0.0'
 icon: litestar-asyncpg.svg
 stars: 14
-monthly_downloads: 884
+monthly_downloads: 911
 latest_version: 0.5.0
 updated_at: '2025-06-24T16:45:09'
 created_at: '2023-10-01T23:31:27'

plugins/litestar-granian.yml

@@ -16,7 +16,7 @@ compatibility:
   litestar: '>=2.0.0'
 icon: litestar-granian.png
 stars: 42
-monthly_downloads: 65575
+monthly_downloads: 66018
 latest_version: 0.15.0
 updated_at: '2026-04-18T23:15:31'
 created_at: '2023-10-02T01:42:04'

plugins/sqlspec.yml

@@ -16,7 +16,7 @@ compatibility:
   litestar: '>=2.0.0'
 icon: _default_icon.svg
 stars: 76
-monthly_downloads: 10882
+monthly_downloads: 10749
 latest_version: 0.48.2
 updated_at: '2026-05-28T15:34:25'
 created_at: '2024-10-30T00:48:46'

readmes/litestar-mcp.md

@@ -141,7 +141,7 @@ Once configured, your application exposes these MCP-compatible endpoints:
 - `GET /mcp` - Server-Sent Events stream when `Accept: text/event-stream` is provided
 - `POST /mcp` - JSON-RPC endpoint for `initialize`, `ping`, `tools/*`, `resources/*`, and optional task methods
 - `GET /.well-known/mcp-server.json` - MCP server manifest
-- `GET /.well-known/agent-card.json` - Agent card metadata
+- `GET /.well-known/agent-card.json` - Agent metadata card
 - `GET /.well-known/oauth-protected-resource` - OAuth protected resource metadata when auth is configured
 
 **Built-in Resources:**

readmes/litestar-vite.md

@@ -4,7 +4,7 @@ Litestar Vite connects the Litestar backend to a Vite toolchain. It supports SPA
 
 ## Features
 
-- One-port dev: proxies Vite HTTP + WS/HMR through Litestar by default; switch to two-port with `VITE_PROXY_MODE=direct`.
+- One-port dev: proxies Vite HTTP + WS/HMR through Litestar on a single ASGI port by default.
 - Framework-mode support: use `mode="framework"` (alias `mode="ssr"`) for Astro, Nuxt, and SvelteKit. Litestar proxies everything except your API routes.
 - Production assets: reads the Vite manifest from `public/manifest.json` (configurable) and serves under `asset_url`.
 - Type-safe frontends: optional OpenAPI/routes export plus `@hey-api/openapi-ts` via the Vite plugin.