Skip to content

v4.2.1: 4, 2, 1... Liftoff

Latest

Choose a tag to compare

@zzstoatzz zzstoatzz released this 17 Nov 19:12
9536dc9

FastMCP 4.2.1 is a security and correctness patch on top of 4.2.0. It tightens OAuth and token handling: JWTs aren't accepted before their nbf, provider required_scopes survive a custom verifier, pre-registered OAuth clients can be pinned to their issuer, and consent, metadata forwarding and upstream claims in the OAuth proxy are hardened. It also raises the opentelemetry-api floor past a traceparent ReDoS. If you install with pip and also have opentelemetry-sdk, upgrade it alongside FastMCP (pip install -U fastmcp opentelemetry-sdk). In require_authorization_consent="remember" mode, users are asked for consent once more per client after upgrading.

Thanks to our 5 contributors, including 2 first-time contributors.

What's Changed

Security 🔒

Fixes 🐞

  • Keep middleware edits to a returned CallToolResult by @Max17190 in #6520
  • fix(resources): coerce template parameters from resolved hints by @67-luck in #6471

Enhancements ✨

Docs 📚

  • Add 4.2 to the what's new page and match the 4.2.0 changelog to the release by @zzstoatzz in #6493

Other Changes 🦾

  • Fix nightly upgrade checks: declare httpx, adopt ty 0.0.100 by @zzstoatzz in #6517
  • Give triage's assess agent public facts about the people on an issue by @zzstoatzz in #6486
  • Restore Marvin labeling and reopen disputed duplicates by @zzstoatzz in #6495
  • chore(deps): Update dependency opentelemetry-api to v1.45.2 [SECURITY] by @prefect-renovate[bot] in #6505
  • chore(deps): Update dependency dnspython to v2.9.2 [SECURITY] by @prefect-renovate[bot] in #6506

New Contributors

Full Changelog: v4.2.0...v4.2.1