Changelog
Release history of ratel-ai-telemetry.
ratel-ai-telemetry release history · crates.io · source · docs.rs
Synced verbatim from the package's
CHANGELOG.mdatratel-ai/ratel@d8635d5— do not edit by hand. Regenerate withpnpm sync:apiinapps/docs.
All notable changes to ratel-ai-telemetry (the Rust telemetry constants crate) are documented here.
The format follows Keep a Changelog and this package adheres to Semantic Versioning.
[0.1.1] - 2026-07-26
Added
GEN_AI_SYSTEM_INSTRUCTIONS,GEN_AI_INPUT_MESSAGES,GEN_AI_OUTPUT_MESSAGES, andRATEL_TOOL_EXECUTION_DETAILSEventRecord constants.
Changed
- Clarify that content events use the OpenTelemetry Logs Event API and that inference output messages require
finish_reason. RATEL_ORIGINis now specified for third-partygen_ai.*spans that a framework adapter overlays, not just Ratel's own search/invoke spans. The constant, itsdirect | agentvalues, andSEMCONV_VERSIONare unchanged; only the shared vocabulary spec widened (CONVENTIONS.md).
[0.1.0] - 2026-07-06
Added
- The telemetry vocabulary (ADR-0015): the full
ratel.*constants (attribute keys, span/event names,gen_ai.*interop keys, and theOrigin/SearchTarget/AuthOutcomevalue enums) pinned to OpenTelemetry semconvgen_aiv1.42.0, as zero-dependency&strconstants and enums. - The
contract-against-the-pintest suite: every constant is asserted against its pinned wire key, so the vocabulary cannot drift fromCONVENTIONS.md.
Changed
- Released as an independent crates.io unit under the
telemetry-core-v*tag prefix.
This crate is constants-only; the TS and Python helpers ship init().