You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,19 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [0.9.2] - 2026-06-11
9
+
10
+
### Added
11
+
12
+
- W3C Trace Context support (`logtide_sdk.tracecontext`): `parse_traceparent`, `format_traceparent`, `generate_trace_id`, `generate_span_id`, `resolve_trace_id` — all exported from the package root
13
+
- All log methods (sync and async) accept keyword-only `trace_id` and `span_id`, sent as top-level fields
14
+
-`LogEntry.span_id` field, serialized as top-level `span_id`
15
+
16
+
### Changed
17
+
18
+
-**Middleware (Flask, Django, Starlette/FastAPI) now resolve the inbound trace context per the W3C spec**: `traceparent` header first, legacy `X-Trace-ID` as deprecated fallback, otherwise a new W3C trace ID is generated. The resolved trace ID is sent as the top-level `trace_id` field instead of `metadata["trace_id"]`, so trace correlation in the platform UI now works for middleware logs
19
+
- Auto-generated trace IDs (`auto_trace_id`, `with_new_trace_id`) are now 32-char lowercase-hex W3C IDs instead of UUIDs
0 commit comments