Skip to content

v1.3.7

Latest
Latest

Choose a tag to compare

View all tags
@keith-axe keith-axe released this 21 Aug 18:40
v1.3.7
3a42557

Added

  • Projects can now be listed and managed through the Management API and MCP server, matching what was already available elsewhere.
  • Proxy responses now include an X-MVGC-Upstream-Path header showing the exact path a request was forwarded to, making provider-side errors easier to diagnose.
  • Gemini requests now support both Google's native API and its OpenAI-compatible endpoint, with the correct authentication automatically selected for each.
  • Policy conditions now support not_regex, the negated form of regex, for excluding matches by pattern.
  • Qwen's US (Virginia) endpoint is now supported for routing and pricing.

Security

  • Alert channel webhook URLs are now masked in API and console responses after creation, matching how connector credentials are already protected.

Fixed

  • Self-hosted gateways connected to the Axemere control plane now clearly reject attempts to edit base provider pricing directly, instead of silently accepting the change and having it overwritten by the next pricing sync.
  • Management API keys and MCP keys created through the console now actually work for authentication — previously a newly created key always failed to authenticate against the Management API or MCP server.
  • Policy bundle load failures no longer expose internal error details in denial reasons; you'll see a clear, actionable message instead.
  • Qwen credentials using a region-specific workspace endpoint now resolve pricing correctly instead of being left unpriced.
  • Credentials with a region or custom base URL override now actually apply when the gateway routes a request, instead of being silently ignored after being saved.
  • AWS Bedrock requests can now use either SigV4 credentials (access key/secret) or a Bedrock API key, instead of only SigV4.
  • Zhipu (GLM) requests routed through its api.z.ai endpoint are now recognized and priced correctly, instead of being rejected as an unrecognized host.
  • Together AI's routing policy now points at its correct API host (api.together.ai) instead of a retired domain (api.together.xyz).

Removed

  • The ByteDance/Doubao (Volcengine Ark) provider has been removed; it's no longer available to configure.
Assets 22
Loading