What this means for your project
The release changes the default redirect policy to same-origin for the affected HTTP transports. If a configured MCP URL redirects to a different origin, check the documented endpoint and transport configuration; do not solve the failure by blindly forwarding credentials across origins. Add a redirect case to the integration test and confirm the expected error type. This is a documented migration concern, not evidence that a particular deployment is broken.
Context reviewed 2026-10-16 against the original release notes ↗. This is guidance for the version above, not a claim that it is the latest release.