otel_auto_route 0.2.0

OpenTelemetry instrumentation for `package:auto_route`. An AutoRouterObserver that emits a span per stack transition AND per tab transition - tabbed apps do not lose views.

Changelog

0.2.0 - 2026-10-11

Changed

• Requires dartastic_opentelemetry_api >=1.0.0-rc.4 <1.0.0-rc.5.
• Breaking: depends on dartastic_opentelemetry_api only, no longer on the SDK. The application chooses and initializes the OpenTelemetry SDK. Parameters and fields typed with SDK classes now use the API types (APITracer, APISpan, APILogger, ...); SDK instances are still accepted wherever an API type is expected.

0.1.0 - 2026-08-08

Added

• OTelAutoRouterObserver — a real AutoRouterObserver subclass (previously a typedef alias for a plain NavigatorObserver). The subclass receives auto_route's didInitTabRoute / didChangeTabRoute callbacks and emits route.tab_init:<path> / route.tab_change:<path> spans with navigation.action and navigation.route.path (+ navigation.previous_route_path) — tab switches in AutoTabsRouter apps are no longer silently lost views. Stack transitions (push / pop / replace / remove) emit route.<transition>:<path> spans of the same shape.
• AutoRouteSemantics — typed navigation.* attribute keys, pinned by a wire-format test. Key strings are wire-identical to the sibling otel_go_router integration, so a mixed go_router + auto_route codebase produces one uniform trace vocabulary.

Changed

• Decoupled from otel_go_router: the dependency (and its path dependency_override + publish-order chain) is gone — competing routers must not be coupled, and auto_route users no longer transitively install go_router. The shared route semantics are inlined as AutoRouteSemantics; the wire contract is the key strings, pinned by test, not a shared symbol.
• Raised SDK floor to dartastic_opentelemetry ^1.1.0-beta.12.
• Widened auto_route to >=9.0.0 <12.0.0 (analyze + tests green against both 9.0.0 and 11.1.0).