[lesnik512]

Closes #315.

The OpenTelemetry extras now require api, sdk and exporters 1.42 and instrumentation 0.63b0, up from 1.28 and 0.49b0. Every *-otl extra moves together, since each instrumentation package pins opentelemetry-instrumentation to its own exact version. The new floors let two shims go:

• FastMCP passes its excluded URLs to OpenTelemetryMiddleware as a comma-joined string, the way FastAPI already does, and no longer imports parse_excluded_urls. At 0.63b0 the middleware takes ExcludeList | str | None and parses a string itself (asgi/__init__.py:582,664).
• PyroscopeSpanProcessor.force_flush is gone. At sdk 1.42.0 the base SpanProcessor.force_flush returns True, which is what the override did.

I checked both against the v1.42.0 and v0.63b0 sources, and that 0.63b0's opentelemetry-semantic-conventions pins opentelemetry-api==1.42.0, so the two floors pair up. The otl comment in pyproject.toml now explains why the floor is 1.42 rather than 0.49b0's pkg_resources reason. ADR 0008 names the new floor.

Tests

None are new. As the issue says, no behaviour changes: the existing suite covers both code paths, and the floors job covers the new floors. The deleted override was # pragma: no cover, so coverage stays at 100%.

The full suite passes, 551 tests at 100% coverage (just test-ci). just lint (including ty), just adr-check and just docs-build pass too.

I ran the floors job's steps locally for all 23 target and interpreter combinations: five targets on 3.11 to 3.14, and free, fastapi and faststream on 3.15. All 23 resolve opentelemetry-sdk 1.42.0 and opentelemetry-instrumentation 0.63b0 and pass scripts/floor_smoke.py.

Breaking changes

A project pinned to OpenTelemetry below 1.42 or instrumentation below 0.63b0 can't install 2.0. opentelemetry-sdk 1.42.0 was released on 2026-05-19.