1.12.0

Breaking changes

Litestar tracing now goes through Litestar's own OpenTelemetryPlugin (#279). If you use LitestarBootstrapper with OpenTelemetry:

• The litestar-otl extra requires litestar>=2.22. With an older Litestar and OpenTelemetry installed, the OpenTelemetry instrument is skipped with a dependency warning.
• opentelemetry_excluded_urls entries are searched in the request path, not the full URL. Path fragments such as /items/\d+$ behave as before; a pattern anchored on scheme or host (^https?://...) no longer matches.
• Requests to unmatched paths, which used to produce no server span, now produce one named after the HTTP method alone (GET), without http.route.
• OTEL_PYTHON_LITESTAR_EXCLUDED_URLS is now honored.

What's Changed

• ci: drop the free-threaded 3.13t leg by @lesnik512 in #271
• ci: use the shared scheduled-failure report by @lesnik512 in #273
• docs: document resource detectors and Sentry profiling on free-threaded CPython by @lesnik512 in #275
• docs: add a tested Taskiq worker recipe built on FreeBootstrapper by @lesnik512 in #276
• fix: annotate context managers with Generator for ty 0.0.85 by @lesnik512 in #278
• feat!: trace Litestar through its own OpenTelemetryPlugin by @lesnik512 in #279
• feat: trace FastMCP HTTP requests with OpenTelemetry by @lesnik512 in #280
• feat: record FastMCP HTTP request and tool call metrics by @lesnik512 in #281

Full Changelog: 1.11.0...1.12.0