Skip to content

Commit cc5ae1f

Browse files
docs(changelog): scrub profile-field noise [skip-runtime-e2e] (#34)
The profile field added in PR #2013 / SDK PR #161 work was removed in PR #33 before any v0.2.0 tag shipped to crates.io. Customer-facing CHANGELOG should reflect what users experience, not internal flaps. Net effect of this scrub: - Delete the [0.2.1] CHANGELOG section entirely. - Revert version bump 0.2.1 → 0.2.0 in Cargo.toml. - Cargo.lock refreshed via cargo build. The [0.2.0] section already had no profile mentions (Rust SDK never shipped the field standalone — Session C's v0.2.0 came in fresh after the v1 schema work, and PR #33 reverted it before tag). Code state unchanged — main has the post-#33 telemetry surface. Signed-off-by: Saurabh Jain <saurabhjain1592@gmail.com>
1 parent 6823403 commit cc5ae1f

3 files changed

Lines changed: 2 additions & 8 deletions

File tree

CHANGELOG.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10-
## [0.2.1] - 2026-05-08
11-
12-
### Removed
13-
14-
- Telemetry `profile` field — collided with the existing `AXONFLOW_PROFILE` governance env var (`platform/agent/profile.go`, ADR-036), which has been the canonical lever for selecting policy-enforcement profile (`dev` / `default` / `strict` / `compliance`) since v6. Reusing the same env var as a free-form telemetry dimension would have caused the v1 telemetry validator to reject any value outside `dev` / `prod` / `unknown` while the governance engine accepted its own four-value allowlist — a customer-visible HTTP 400 on every `AXONFLOW_PROFILE=strict` deployment. The dimension also had no consumer in the central pipeline (no aggregator, no daily-report column, no dashboard), and `deployment_mode` already covers the topology axis it was meant to add. `AXONFLOW_PROFILE` reverts to its single original purpose; the SDK no longer reads it for telemetry.
15-
1610
## [0.2.0] - 2026-05-08 — Decision history API + central telemetry parity
1711

1812
**Preview release.** The headline feature is the new decision-history client API

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "axonflow-sdk-rust"
3-
version = "0.2.1"
3+
version = "0.2.0"
44
edition = "2021"
55
rust-version = "1.78"
66
description = "Rust SDK for the AxonFlow AI governance platform"

0 commit comments

Comments
 (0)