Skip to content

chore(release): v8.2.0 platform cross-ref + terminology #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
saurabhjain1592 merged 1 commit into from
May 23, 2026
Merged

chore(release): v8.2.0 platform cross-ref + terminology #205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,9 @@ No breaking changes. New imports are additive in `axonflow.hitl`. The
existing `get_hitl_request` / `approve_hitl_request` /
`reject_hitl_request` methods are unchanged.

Requires AxonFlow platform >= 8.1.0 for `notify_url` webhook delivery
and `Idempotency-Key` request deduplication.

## [8.1.0] - 2026-05-22 — `X-Client-ID` header on every outbound request + `org_id` in telemetry heartbeat

Companion release to the v9 identity cleanup on the platform. Every
Expand All @@ -76,7 +79,7 @@ when no `client_id` is configured.
SDK telemetry up to parity with the platform — every heartbeat now
identifies which deployment-organization emitted it. Two sources in
precedence order:
1. The `ORG_ID` env var when set (the operator's explicit configuration
1. The `ORG_ID` env var when set (the explicit configuration
on self-hosted deployments, or the `cs_<uuid>` tenant identifier on
Community SaaS).
2. Otherwise the `local-dev-org` sentinel (default-config Community-mode
Expand All @@ -91,7 +94,7 @@ when no `client_id` is configured.

- **Telemetry-enabled log line** softened from "anonymous telemetry
enabled" to "telemetry enabled" to stay coherent with the `org_id`
addition — the operator-supplied `ORG_ID` on self-hosted is not
addition — the configured `ORG_ID` on self-hosted deployments is not
anonymized; only the `instance_id` and `cs_<uuid>` Community SaaS
identifier remain anonymous-by-design.

Expand Down
Loading