v0.1.82 — 25 Jun 2026
Performance — Eliminated redundant Supabase calls per API request
Who is affected: All API consumers. No request/response contract changes — this is an internal performance improvement.
What was wrong
A single GET /api/items/:collection request could trigger 21 Supabase round-trips. Auth, user-status, and policy lookups were repeated independently by each service factory and permission function within the same request.
What changed
A per-request context (RequestContext) is now computed once and shared across all service factories and permission checks within the same request. Auth and policy results are cached for the lifetime of the request only.
Before / After
| Endpoint | Supabase calls before | Supabase calls after | Latency improvement |
|---|---|---|---|
GET /api/items/:collection | 21 | 9 | ~70% |
GET /api/users | 20 | 15 | ~16% |
Last updated on