chore(release): v4.2.1 — fix Python SDK wheel build#80
Merged
Conversation
The 4.2.0 release published to crates.io and npm but the Python SDK wheel build failed (so PyPI + GitHub Release were skipped): error[E0063]: missing field `allow_manual_delegation` in initializer of `AutoDelegationConfig` The `PyAutoDelegationConfig -> AutoDelegationConfig` conversion used a struct literal that didn't include the `allow_manual_delegation` field added to the core config. Core CI never caught it because the SDKs are excluded from the core workspace and only built at release time (maturin). The Node SDK was fine — it builds the config via `Default::default()` + field assignment. Fix: the Python conversion now uses `..Default::default()` for fields it does not expose, so new core fields can't break the wheel build again. Verified the Python SDK compiles. Version bumped 4.2.0 -> 4.2.1 to complete the release across all channels.
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
2 participants
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.
Completes the 4.2.0 release. crates.io + npm published fine, but the Python SDK wheel build failed (so PyPI + GitHub Release were skipped):
Cause: PR #76 added
allow_manual_delegationtoAutoDelegationConfig, but the Python SDK'sPyAutoDelegationConfig → AutoDelegationConfigconversion uses a struct literal that didn't include it. Core CI never caught this — the SDKs are excluded from the core workspace and only built at release time (maturin). (The Node SDK was fine: it builds viaDefault::default()+ field assignment.)Fix: the Python conversion now uses
..Default::default()for fields it doesn't expose, so future core fields can't break the wheel build. Verified the Python SDK compiles (cargo build --manifest-path sdk/python/Cargo.toml).Version bumped 4.2.0 → 4.2.1 across the CI-enforced surface + CHANGELOG. Tagging
v4.2.1re-runs the full release (crates.io + npm + PyPI + GitHub Release) to complete delivery across all channels.Follow-up (not in this PR): add an SDK build step to core CI so SDK-breaking core changes are caught before release.