From d1424479d6e1b9389bf624e4fcc2fd56331f4cb4 Mon Sep 17 00:00:00 2001 From: Saurabh Jain Date: Fri, 8 May 2026 20:49:34 +0200 Subject: [PATCH] docs(changelog): scrub profile-field noise [skip-runtime-e2e] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The v1-telemetry profile field never reached any tagged customer release — it landed in v1.4.0 prep on the same day (2026-05-08) that the AXONFLOW_PROFILE collision was caught (axonflow-enterprise#2033) and removed via PR #63 before any tag shipped. Per user direction: "This never made it to any customer so why it should be in changelog when we removed it already before the release." Doc-only correction: - CHANGELOG.md: deleted the [1.4.1] removal entry (no longer narrating a removal of a field that never shipped); scrubbed the "profile from AXONFLOW_PROFILE" clause from the [1.4.0] v1 schema bullet (telemetry_type / endpoint_type / AXONFLOW_TRY remain). - .codex-plugin/plugin.json + .codex-plugin/marketplace.json (metadata + plugins[0]): 1.4.1 -> 1.4.0. Linked: - axonflow-enterprise#2033 (root issue) - #63 (per-repo profile-removal PR; merged) Self-review: - Diff hunk-by-hunk: 3 surfaces touched, all 1.4.1 -> 1.4.0 reverts + the [1.4.1] section removal + 1 word-level scrub in [1.4.0]. - Both JSON files re-validated with python3 -m json.tool. - No other 1.4.1 references in the repo. Skip-runtime-e2e justification: Doc-only changelog scrub + version revert. No runtime code paths or shipped artifacts change. The plugin's runtime behaviour at the eventual tagged version (1.4.0) is identical pre/post this PR. Signed-off-by: Saurabh Jain --- .codex-plugin/marketplace.json | 4 ++-- .codex-plugin/plugin.json | 2 +- CHANGELOG.md | 18 +----------------- 3 files changed, 4 insertions(+), 20 deletions(-) diff --git a/.codex-plugin/marketplace.json b/.codex-plugin/marketplace.json index 61326c2..039b461 100644 --- a/.codex-plugin/marketplace.json +++ b/.codex-plugin/marketplace.json @@ -7,14 +7,14 @@ }, "metadata": { "description": "Runtime governance for OpenAI Codex. Policy enforcement on terminal commands, advisory governance via skills, PII detection, audit trails, and compliance-grade decision records.", - "version": "1.4.1" + "version": "1.4.0" }, "plugins": [ { "name": "axonflow", "source": "./", "description": "Policy enforcement, PII detection, and audit trails for OpenAI Codex. Hybrid governance — enforces policies on terminal commands (exec_command) via hooks, provides advisory governance for other tools via implicit-activation skills, and records compliance-grade audit trails. Self-hosted via Docker — all data stays on your infrastructure.", - "version": "1.4.1", + "version": "1.4.0", "author": { "name": "AxonFlow", "email": "hello@getaxonflow.com", diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json index 51bf305..0270066 100644 --- a/.codex-plugin/plugin.json +++ b/.codex-plugin/plugin.json @@ -2,7 +2,7 @@ "name": "axonflow", "displayName": "AxonFlow Governance", "description": "Policy enforcement, PII detection, and audit trails for OpenAI Codex. Hybrid governance — enforces policies on terminal commands (exec_command) via hooks, provides advisory governance for other tools via implicit-activation skills, and records compliance-grade audit trails. Self-hosted via Docker — all data stays on your infrastructure.", - "version": "1.4.1", + "version": "1.4.0", "author": { "name": "AxonFlow", "email": "hello@getaxonflow.com", diff --git a/CHANGELOG.md b/CHANGELOG.md index dcac07e..2ea281d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,22 +2,6 @@ ## [Unreleased] -## [1.4.1] - 2026-05-08 - -### Removed - -- Telemetry `profile` field and the `AXONFLOW_PROFILE` env-var read in - `scripts/telemetry-ping.sh`. The v1 schema reused `AXONFLOW_PROFILE`, - which already governs runtime policy enforcement (`dev | default | - strict | compliance`); the two name-spaces collided and a customer - setting `AXONFLOW_PROFILE=strict` would have had their heartbeat - rejected by the checkpoint validator. The field had no consumer on - the analytics side, and `deployment_mode` already covers the - topology dimension it was meant to add. Heartbeat payload no longer - emits `profile`; matching assertion removed from - `tests/heartbeat-real-stack/run_real_stack.sh`. `AXONFLOW_PROFILE` - reverts to its original governance-only meaning. - ## [1.4.0] - 2026-05-08 ### Added @@ -26,7 +10,7 @@ ### Telemetry -- v1 schema (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `profile` from `AXONFLOW_PROFILE`; plus `AXONFLOW_TRY=1` to force `deployment_mode=community_saas` for tenants behind custom hostnames. +- v1 schema (axonflow-enterprise#2008): heartbeat now emits `telemetry_type: "plugin"`, `endpoint_type` (`localhost | private_network | remote | unknown`), and `AXONFLOW_TRY=1` to force `deployment_mode=community_saas` for tenants behind custom hostnames. - `deployment_mode` allowlist normalised to `self_hosted | community_saas | unknown` (was `production`/`development`/`community-saas`). Analytics queries on the legacy values must update. ## [1.3.0] - 2026-05-07 — V1 Plugin Pro upgrade-prompt envelope + 5 new MCP tools surfaced