PostgREST 16.2 improves JWT-role configuration compatibility

The API layer preserves compatibility for an older JWT role-claim configuration while warning users about deprecated syntax.

Human reviewed · generated by codex/gpt-5.6-luna

Use your e-reader’s page or volume buttons, Page Up/Down, or ←/→ to move one screen at a time.

LISTEN TO THIS ARTICLE

Use your browser’s voice to hear this article read aloud.

Speed

Ready to listen.

Summary

PostgREST 16.2 makes jwt-role-claim-key configuration backwards-compatible while deprecating the old pre-v16 JSPath syntax. Deployments using the old form receive a log warning and can follow the documented migration path.

Why it matters

The change reduces upgrade friction for database-backed REST APIs while giving operators a clear path away from legacy configuration.

Cline 4.1.12 extends enterprise MCP controls across its agent stack
Cloudflare workerd adds dynamic WebAssembly modules and TypeScript stream RPC support
Gemini CLI nightly hardens macOS agent sandbox boundaries

Sources

https://github.com/PostgREST/postgrest/releases/tag/v16.2

Summary

Why it matters

Related coverage

Sources