Repository navigation
4.1.0
Adds optional execution tracing and log correlation behind the telemetry feature. Applications own OpenTelemetry providers, propagators, sampling and exporters. Default features do not require OpenTelemetry. Carrier propagation requires an actually advertised Server capability; unsupported Servers use independent task traces.
This release includes durable signal/update request IDs from #109 and retains the published Rust 4 workflow and cancellation contracts.
Normal protected crates.io publication, exact registry checksum verification and installed consumer gates pass. A normal registry consumer against immutable Server 2.9.11 completes through two independent workers, preserves the business result/request ID, emits four task/attempt spans and three correlated callback logs, restores scope and exits cleanly. Server 2.9.11 has no carrier capability, so this proves fallback task tracing rather than durable caller propagation.
See the telemetry API and #110. Complete Server and cross-SDK delivery remains tracked in Workflow #773.