ZyyandCodex 45903b684b fix(admin): remove config revision fences from API writes ...

Operator mutations no longer require callers to carry configRevision values through accounts, client keys, provider credentials, or settings. The store and admin use cases now apply current state directly, which removes stale-revision failures from normal create, update, and delete flows.

xAI Responses catalog entries now let the upstream validate feature support instead of rejecting requests locally when optional catalog metadata is absent, matching the Build routing behavior used by grok2api.

Co-authored-by: Codex <noreply@openai.com>

2026-07-27 11:30:59 +08:00

..

gateway-admin

fix(admin): remove config revision fences from API writes

2026-07-27 11:30:59 +08:00

gateway-api

fix(admin): remove config revision fences from API writes

2026-07-27 11:30:59 +08:00

gateway-core

fix(core): stop deadline expiry from tripping the circuit and unpin recovery account

2026-07-27 02:25:47 +08:00

gateway-host

chore(release): drop Windows target, extend stop grace, document single-replica

2026-07-27 02:26:25 +08:00

gateway-protocol

perf(protocol,api): incremental SSE scanning and map-based frame decode

2026-07-26 20:09:57 +08:00

gateway-store

fix(admin): remove config revision fences from API writes

2026-07-27 11:30:59 +08:00

providers

fix(admin): remove config revision fences from API writes

2026-07-27 11:30:59 +08:00