chore(sdk): bump SDK patch version 0.9.4 -> 0.9.5#538
Merged
Conversation
Bump the workspace package version (Rust `boxlite`, C, Python, Node crates) plus the published Python (pyproject.toml) and Node (package.json) package versions. Go SDK is versioned via git tag, so no in-tree change is needed.
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
Patch-bump the SDK version 0.9.4 → 0.9.5 across the published surfaces:
Cargo.toml[workspace.package]+ the 6 internal path-dep pins (covers the Rustboxlite, C, Python-rust, Node-rust crates)Cargo.lock(12 workspace crate entries; unrelatedrand0.9.4 untouched)sdks/python/pyproject.toml,sdks/node/package.jsonRebased on
mainafter the Node REST-binding fix (#536) landed.Notes
Local pre-push gate skipped (
--no-verify, explicitly authorized): the gate runs the full Rust integration suite becauseCargo.lockchanged; it passed 224/224 earlier this session, and a subsequent failure was an environmental/flaky VM/image-pull issue. A version-string-only change cannot affect Rust integration behavior. GitHub CI on this PR is the authoritative gate.Test plan
randuntouched)