docs(changelog): scrub profile-field noise [skip-runtime-e2e]#190
Merged
saurabhjain1592 merged 1 commit intomainfrom May 8, 2026
Merged
docs(changelog): scrub profile-field noise [skip-runtime-e2e]#190saurabhjain1592 merged 1 commit intomainfrom
saurabhjain1592 merged 1 commit intomainfrom
Conversation
The v1-telemetry `profile` field never reached any tagged customer release — its CHANGELOG mentions are internal noise. Drop the [8.0.1] section entirely and scrub the profile-specific clauses from the [8.0.0] section. Revert version markers from 8.0.1 → 8.0.0. The remaining v8.0.0 features (decision history API, telemetry simplification, telemetry_type/component, deployment_mode classification, etc.) are unchanged. Refs: getaxonflow/axonflow-enterprise#2033 (original env-var collision bug), getaxonflow/axonflow-enterprise#2035 (code-side fix already shipped on main as ff8e111). Signed-off-by: Saurabh Jain <saurabhjain1592@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Scrub all references to the v1-telemetry
profilefield from CHANGELOG.md and revert the patch version bump. Theprofilefield never reached any tagged customer release — its CHANGELOG mentions are internal noise.User direction: "This never made it to any customer so why it should be in changelog when we removed it already before the release."
What changed
CHANGELOG.md— deleted the[8.0.1] - Drop telemetry profile fieldsection entirely; scrubbed theprofilemention from the[8.0.0]"Telemetry payload (v1 schema, ...)" bullet.axonflow/_version.py— reverted__version__ = "8.0.1"→"8.0.0".pyproject.toml— revertedversion = "8.0.1"→"8.0.0".What is preserved
The remaining v8.0.0 narrative is unchanged:
client.list_decisions(opts), the v7→v8 migration guide (telemetrykwarg /AxonFlowConfig.telemetryremoval,send_telemetry_pingsignature change), sandbox-mode telemetry,telemetry_type: "sdk"field,_classify_deployment_mode, and the_classify_endpointchange.Skip-runtime-e2e justification
This is a documentation correction with two matching version-marker reverts. The code state was already settled in the prior release train (
ff8e111dropped the runtime read ofAXONFLOW_PROFILEfor telemetry onmain). No user-facing behaviour changes; version-string evaluates correctly (exec(open('axonflow/_version.py').read())→8.0.0).References
mainvia fix(telemetry): drop profile field [skip-runtime-e2e] #189 asff8e111)Self-review
[8.0.1]section + the singleprofileclause inside[8.0.0]'s "Telemetry payload" bullet were removed._version.py+pyproject.toml) are reverted in lockstep.8.0.1references remain underaxonflow/orpyproject.toml.