chore(python): sync python crate version to 0.9.5 - #102
Merged
Conversation
The python/ binding crate lived outside the root workspace and was invisible to release-plz, so its version drifted to 0.9.3 while the Rust crate moved to 0.9.5 (and its lockfile still pinned redis-cloud 0.8.0 / redis-cloud-py 0.1.0). Bump python/Cargo.toml and the two local-crate entries in python/Cargo.lock to 0.9.5. Lockfile change is restricted to the version strings — no transitive re-resolution. Closes #68
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.
What
Sync the
python/binding crate to 0.9.5, matching the root Rust crate.python/Cargo.toml:0.9.3 → 0.9.5python/Cargo.lock: local-crate entriesredis-cloud 0.8.0 → 0.9.5,redis-cloud-py 0.1.0 → 0.9.5Why
python/lives outside the root workspace and ispublish = false, so release-plz never sees it — its version and lockfile drift every time the Rust crate is released.Scope
Deliberately minimal: only the version strings change. An initial
cargo update --workspacepass churned ~30 unrelated crates (reqwest 0.12→0.13, ring→aws-lc-rs, jni, …) — reverted, since that overlaps with the separate reqwest migration in #48 and isn't buildable/testable here.Follow-up (not in this PR)
python/into the root workspace so release-plz tracks it.Closes #68