chore(release): v7.7.0 — X-Axonflow-Client header [skip-runtime-e2e]#163
Merged
saurabhjain1592 merged 1 commit intomainfrom May 6, 2026
Merged
chore(release): v7.7.0 — X-Axonflow-Client header [skip-runtime-e2e]#163saurabhjain1592 merged 1 commit intomainfrom
saurabhjain1592 merged 1 commit intomainfrom
Conversation
…se validation [skip-runtime-e2e] Companion release to platform v7.7.0. The Java SDK now sends X-Axonflow-Client: sdk-java/<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 (#161 — header injection). 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. No public API changes. Existing v7.0.x callers update <version>7.7.0</version> and 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 #161 landed. Signed-off-by: Saurabh Jain <saurabhjain1592@gmail.com>
saurabhjain1592
added a commit
that referenced
this pull request
May 6, 2026
…[skip-runtime-e2e] (#164) Companion to axonflow-sdk-{go,python,typescript} fix PRs (#156, #183, #215). Previous release PR #163 bumped Java SDK from v7.0.0 directly to v7.7.0 to platform-align with V1 SaaS Plugin Pro launch — incorrect semver. Only one substantive feature since v7.0.0 (X-Axonflow-Client header injection in #161), so natural bump is v7.1.0. Updates: - pom.xml <version> 7.7.0 → 7.1.0 - CHANGELOG header [7.7.0] → [7.1.0], 2026-05-06 stamp preserved - Sister SDK refs (Go / Python / TypeScript) updated to v7.1.0 - Platform v7.7.0 refs in same entry kept (those are correctly the platform version) [skip-runtime-e2e] — version-correction only; no behavior change since the header injection runtime contract was already validated when #161 landed and re-confirmed when #163 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.
Companion release to platform v7.7.0 (V1 SaaS Plugin Pro launch). The Java SDK gains the
X-Axonflow-Client: sdk-java/<version>header on every governed request.Single substantive change since v7.0.0: #161 (header injection). Other commits (#160 DCO docs, #162 definition-of-done CI gate, #158 v7.0.0 changelog typo) are infrastructure / docs.
Compatibility
<version>to 7.7.0 in your dependency blockSelf-review
pom.xml7.0.0 → 7.7.0;SDK_VERSIONreads from Maven pom.properties at runtime so no Java source change neededSkip-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.