Repository navigation
v0.27.8
One security fix, no breaking changes. yoagent-rutis (0.13.0) and yoagent-workers (0.4.0) are unchanged.
- Provider requests no longer follow a redirect to another host. A provider answering with a redirect to another origin had the request re-sent there with every header except
Authorization,CookieandProxy-Authorization. That carried the key from Anthropic (x-api-key), Azure (api-key), Gemini (x-goog-api-key), Bedrock's session token (x-amz-security-token) and any credential inModelConfig::headers; a 307 or 308 carried the whole prompt too, on every retry. Every provider and decision backend now follows redirects only within the request's own origin (scheme, host and port), as the MCP HTTP transport already did by default. A redirect elsewhere fails at once, naming the other origin, and is not retried. Native targets only: on wasm32 the host'sfetchfollows redirects itself. (#451)