Skip to content

Commit f84ffbe

Browse files
lesnik512claude
andauthored
docs(release): finalize 1.3.0 notes (fastmcp on 3.14t, api/sdk fix) (#157)
The 1.3.0 note was written at the start of the arc and understated what shipped: fastmcp now imports and runs on the 3.14t leg (only 3.13t is cffi-blocked), and the api/sdk conflation fix that made lite-bootstrap[fastmcp] importable was missing from the bug-fix list. release.yml uses this file verbatim as the GitHub Release body. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 31f79b3 commit f84ffbe

1 file changed

Lines changed: 20 additions & 8 deletions

File tree

‎planning/releases/1.3.0.md‎

Lines changed: 20 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,13 @@ plus two import-safety fixes surfaced while verifying it.
1212
was the mandatory `orjson` dependency (below). Core, `logging`, `sentry`,
1313
`fastapi`, and `faststream` (plus their `-sentry`/`-logging`/`-metrics`
1414
combos) now install and run on both 3.13t and 3.14t. `litestar` (+
15-
`litestar-metrics`) lands on **3.14t only** — `msgspec`, which `litestar`
16-
requires unconditionally, gates free-threaded support to Python 3.14+ and
17-
fails to build from source on 3.13t. `fastmcp` (+ `fastmcp-metrics`), `otl`
18-
(the gRPC OTLP exporter needs `grpcio`, which has no ft wheels), and
19-
`pyroscope` (`pyroscope-io` is abi3-only and unmaintained) remain
20-
unavailable on free-threaded builds pending upstream fixes. See
15+
`litestar-metrics`) and `fastmcp` (+ `fastmcp-metrics`) land on **3.14t
16+
only** — `msgspec` (litestar) and `cffi` (fastmcp, via cryptography) both
17+
gate free-threaded support to Python 3.14+ and fail to build from source on
18+
3.13t. The gRPC `otl` exporter (`grpcio` has no ft wheels — use the new
19+
`otl-http` extra instead) and `pyroscope` (`pyroscope-io` is abi3-only and
20+
unmaintained) remain unavailable on free-threaded builds pending upstream
21+
fixes. See
2122
[`architecture/free-threading.md`](../../architecture/free-threading.md) for
2223
the full support matrix and [`planning/deferred.md`](../deferred.md) for the
2324
ecosystem blockers.
@@ -60,8 +61,17 @@ plus two import-safety fixes surfaced while verifying it.
6061
is absent, `bootstrap()` emits an `InstrumentDependencyMissingWarning` naming
6162
the extra to install (`[otl]` for gRPC, `[otl-http]` for HTTP); see
6263
[`architecture/instruments.md`](../../architecture/instruments.md).
64+
- **The OpenTelemetry instrument no longer assumes the SDK is present when only
65+
the API is.** `is_opentelemetry_installed` (`find_spec("opentelemetry")`) is
66+
true with just `opentelemetry-api`, but the instrument imports
67+
`opentelemetry.sdk.*` — a separate distribution. An api-only environment
68+
(e.g. `lite-bootstrap[fastmcp]`) therefore still crashed at the sdk import
69+
even after the exporter guard above. A new `is_opentelemetry_sdk_installed`
70+
flag gates the sdk imports, and `check_dependencies()` requires both the api
71+
and the sdk. With all three fixes, `lite-bootstrap[fastmcp]` imports and runs
72+
on free-threaded 3.14t.
6373

64-
Both bugs are not ft-specific — they affect any environment with a partial
74+
These bugs are not ft-specific — they affect any environment with a partial
6575
`opentelemetry` stack — but ft verification work is what surfaced them.
6676

6777
## Backwards compatibility
@@ -73,4 +83,6 @@ build once `orjson` is installed (directly, or via the `[orjson]` extra).
7383

7484
## References
7585

76-
- Design bundle: `planning/changes/2026-07-18.01-free-threaded-python-support.md`
86+
- Design bundle: `planning/changes/2026-07-18.01-free-threaded-python-support.md`,
87+
`planning/changes/2026-07-19.01-fix-otel-api-sdk-conflation.md`,
88+
`planning/changes/2026-07-19.02-otlp-http-exporter.md`.

0 commit comments

Comments
 (0)