release: Python SDK v6.7.0#158
Merged
saurabhjain1592 merged 3 commits intomainfrom Apr 25, 2026
Merged
Conversation
Minor release. Wire-shape canonicalization sweep — purely additive, new fields default to None, deprecated aliases preserved. Bumps: - pyproject.toml + axonflow/_version.py: 6.6.2 -> 6.7.0 - CHANGELOG [Unreleased] -> [6.7.0] - 2026-04-25 Wire-shape baseline regenerated against community SHA 10d44eb4 (post platform v7.4.2 spec corrections). DynamicPolicyInfo entry auto-resolves (spec was wrong, SDK was correct). Regen also surfaces 11 newly-discovered drift entries from the v6.7 sweep that weren't captured in the earlier baseline — these become tracked debt for future burndown per the CONTRIBUTING.md baseline-burndown policy. Net 26 -> 37. Coordinated v6 alignment release: ships same day as TypeScript v6.0.0, Java v6.0.0, Go v5.7.0.
saurabhjain1592
added
the
spec-pin-bump
The earlier regen picked up a stale editable axonflow 6.3.0 install at /opt/homebrew/lib/python3.11/site-packages/__editable__.axonflow-6.3.0.pth that points at a sibling clone, not this worktree. When invoked as "python scripts/refresh.py", sys.path[0] is scripts/ which has no axonflow — so the import falls through to the stale editable install, discovers an old MCPCheckInputRequest with 4 fields, and writes ghost drift into the baseline. CI didn't repro because CI does pip install -e . in the PR checkout itself. After pip install -e . in this worktree, axonflow resolves to the v6.7 code in this branch, the regen produces the correct 25-entry baseline, and only DynamicPolicyInfo auto-resolves vs prior baseline — matching the auto-resolution shape of TS/Go/Java. Net 26 -> 25. Lesson: developer-run regen scripts that import the SDK should use a fresh editable install or fail loudly when sys.modules['axonflow'] is not the worktree they were invoked against. Filing as follow-up.
saurabhjain1592
force-pushed
the
release/v6.7.0
branch
from
3d4ede8 to
af7a2b8
Compare
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
Minor release — wire-shape canonicalization sweep is purely additive (new fields default to `None`, deprecated aliases preserved).
Bumps
Wire-shape baseline regen
Pin SHA bumped `bf1ca22a` → `10d44eb4`. `DynamicPolicyInfo` auto-resolves (spec was wrong; SDK was correct).
Note: regen also surfaced 11 newly-discovered drift entries from the v6.7 sweep that weren't in the prior baseline. They are now tracked debt per the CONTRIBUTING.md baseline-burndown policy. Net 26 → 37.
Coordinated release
Ships same day as TS v6.0.0, Java v6.0.0, Go v5.7.0.
Test plan