v0.2.21

🌟 Release Highlights

This release focuses on timeout correctness for HTTP backends and MCP connection handling — ensuring gateway-configured execution budgets are respected end-to-end.

🐛 Bug Fixes & Improvements

• HTTP backend timeouts now honor configured budgets (#3911): A hardcoded 120-second transport-level cap was silently overriding any tool execution budget set in the gateway config. HTTP backends now correctly respect the configured timeout, preventing unexpected truncations on long-running tools.

• MCP connect timeout uses consistent default (#3946): The 30-second hardcoded connect timeout was replaced with a named defaultConnectTimeout constant, and an invalid <= 0 guard was fixed. This makes timeout behavior predictable and easier to reason about.

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/github/gh-aw-mcpg:v0.2.21
# or
docker pull ghcr.io/github/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

Generated by Release · ● 110.3K

---

What's Changed

• Honor gateway tool execution budgets for HTTP backends by removing hardcoded 120s transport cap by @Copilot in #3911
• [test-improver] Improve tests for tracing package by @github-actions[bot] in #3938
• [test] Add tests for oidc.extractJWTExpiry by @github-actions[bot] in #3939
• [Repo Assist] fix(mcp): replace hardcoded 30s with defaultConnectTimeout constant, fix <= 0 guard by @github-actions[bot] in #3946
• Fix gofmt alignment in jwt_expiry_test.go by @lpcox in #3954
• Fix TestFullDIFCConfigFromJSON timeout waiting for backend connections by @lpcox in #3960
• [Repo Assist] test(mcp): add connect-timeout default behaviour tests by @github-actions[bot] in #3947

Full Changelog: v0.2.20...v0.2.21