Skip to content

docs(changelog): scrub profile-field noise [skip-runtime-e2e]#67

Merged
saurabhjain1592 merged 1 commit intomainfrom
chore/scrub-profile-changelog-noise
May 8, 2026
Merged

docs(changelog): scrub profile-field noise [skip-runtime-e2e]#67
saurabhjain1592 merged 1 commit intomainfrom
chore/scrub-profile-changelog-noise

Conversation

@saurabhjain1592
Copy link
Copy Markdown
Member

Summary

Doc-only correction. The v1-telemetry profile field never reached a tagged customer release — it landed in v1.4.0 prep on the same day (2026-05-08) that the AXONFLOW_PROFILE env-var collision was caught (axonflow-enterprise#2033) and removed via PR #66 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."

Changes

  • CHANGELOG.md: deleted the [1.4.1] removal entry entirely (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 — the rest of the bullet (telemetry_type / endpoint_type / AXONFLOW_TRY) remains.
  • .cursor-plugin/plugin.json: 1.4.11.4.0.

The remaining v1.4.0 features (V1.1 list-recent-decisions skill, tests/test-hooks.sh skill-count fix) STAY.

Linked

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. No runtime-e2e/ paths touched.

Self-review summary

  • Walked the 2-file diff hunk-by-hunk:
    • CHANGELOG.md: removed [1.4.1] block + the profile from AXONFLOW_PROFILE clause from the [1.4.0] Telemetry bullet.
    • .cursor-plugin/plugin.json: line 5 1.4.11.4.0.
  • plugin.json re-validated with python3 -m json.tool.
  • grep -rn "1\.4\.1" confirms no other references remain.
  • DCO sign-off via git commit -s.
  • Title length: 61 chars (≤72 limit).

DO NOT MERGE pending user review.

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 #66 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).
- .cursor-plugin/plugin.json: 1.4.1 -> 1.4.0.

Linked:
- axonflow-enterprise#2033 (root issue)
- #66 (per-repo profile-removal PR; merged)

Self-review:
- Diff hunk-by-hunk: 2 surfaces touched, 1.4.1 -> 1.4.0 revert in
  plugin.json + the [1.4.1] section removal + 1 word-level scrub in
  [1.4.0].
- plugin.json 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 <saurabhjain1592@gmail.com>
@saurabhjain1592 saurabhjain1592 merged commit 0b93a3c into main May 8, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant