chore(release): v7.7.0 — X-Axonflow-Client header [skip-runtime-e2e]#155
Merged
saurabhjain1592 merged 1 commit intomainfrom May 6, 2026
Merged
chore(release): v7.7.0 — X-Axonflow-Client header [skip-runtime-e2e]#155saurabhjain1592 merged 1 commit intomainfrom
saurabhjain1592 merged 1 commit intomainfrom
Conversation
…se validation [skip-runtime-e2e] Companion release to platform v7.7.0. The Go SDK now sends X-Axonflow-Client: sdk-go/<version> on every governed request, which the agent (v7.7.0+) uses to derive SDK request scope and validate against any license token's audience claim per the ADR-050 license matrix. Single substantive change since v7.0.0 (#153 — header injection). The supporting commits since v7.0.0 (DCO sign-off docs, Definition-of- Done CI gate, v7.0.0 changelog typo correction) are infrastructure and not user-facing. Module path stays github.com/getaxonflow/axonflow-sdk-go/v7 — no major bump, no import-path migration. Existing v7.0.x callers rebuild against v7.7.0 with no source changes. Backward-compatible against pre-v7.7.0 agents (header silently dropped). [skip-runtime-e2e] — version + CHANGELOG bump only; the underlying header behavior shipped + was runtime-tested when #153 landed. Signed-off-by: Saurabh Jain <saurabhjain1592@gmail.com>
saurabhjain1592
added a commit
that referenced
this pull request
May 6, 2026
…[skip-runtime-e2e] (#156) The previous release PR (#155) bumped the Go SDK from v7.0.0 directly to v7.7.0 to platform-align with the V1 SaaS Plugin Pro launch. That was incorrect semver — the only substantive change since v7.0.0 is the X-Axonflow-Client header injection (one minor feature), so the natural bump is v7.1.0, not v7.7.0. Platform-aligned SDK versioning was the wrong default — the next minor platform release would force another no-code SDK bump just to keep the numbers in lockstep, decoupling SDK semver from actual SDK changes. The /health endpoint's MinSDKVersion + RecommendedSDKVersion already covers compatibility for users who care about the platform-version relationship. Companion plugin releases stay correct at v1.2.0 / v2.2.0 (those have multiple substantive commits since their last tags so the minor bumps were already semver-true). Updates: - version.go 7.7.0 → 7.1.0 - CHANGELOG header [7.7.0] → [7.1.0], 2026-05-06 stamp preserved - CHANGELOG cross-references to sister SDK versions corrected - Compatibility note: existing v7.0.x callers rebuild against v7.1.0 [skip-runtime-e2e] — version-correction only; no behavior change since the header injection runtime contract was already validated when #153 landed and re-confirmed when #155 merged. 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
Companion release to platform v7.7.0 (V1 SaaS Plugin Pro launch). The Go SDK gains the `X-Axonflow-Client: sdk-go/` header on every governed request, used by the agent (v7.7.0+) to derive SDK request scope and validate against any license token's audience claim.
Changes since v7.0.0
Compatibility
Self-review
Test plan
Skip-runtime-e2e justification
This is a release-prep PR — version manifest bump + CHANGELOG promotion only. The substantive code changes (X-Axonflow-Client header injection for SDKs / V1 paid Pro tier wire-up for plugins) shipped in earlier feature PRs that included their own runtime-e2e tests against a live agent stack. Re-running runtime-e2e for a CHANGELOG and version-string change adds no signal — the runtime contract was validated when the feature commits landed.