Repository navigation
chore(deps): pin canton-lib 0.11.0 - #5
Merged
Merged
Conversation
canton-lib 0.11.0 moves canton-api-client to 3.6.1. The localnet suite depends on canton-api-client directly, so its pin moves too. A project that pins a canton-lib v0.10.0 crate next to this one cannot resolve canton-api-client, so the release is 0.2.0. canton-lib 0.10.1 also makes active_contracts::get return the Ledger API error instead of an empty list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
schronck
approved these changes
Oct 9, 2026
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.
What
This PR pins
canton-lib0.11.0 and prepares thebitsafe-token0.2.0 release.canton-libcrates move fromv0.10.0tov0.11.0.canton-api-clientdev-dependency moves from3.6.0-0.1.0to3.6.1-0.1.0.CHANGELOG.mdand the README install tags move to 0.2.0.Why
canton-lib0.11.0 usescanton-api-client3.6.1, which matches Canton 3.6.1.canton-lib0.10.1 also fixesactive_contracts::get. That function now returns the Ledger API error when the participant rejects a request. Before, it returned an empty list, so a balance query reported 0.The localnet suite uses
canton-api-clientdirectly. Cargo permits only one 3.x version of that crate in a build. So the dev-dependency must move withcanton-lib.Key decision: 0.2.0, not 0.1.1
The Rust API of
bitsafe-tokendoes not change. The exposedJsActiveContractandCreatedEventmodels have the same fields in 3.6.0 and 3.6.1.A downstream project can still break. I built a test crate against this branch:
bitsafe-tokenkeycloakv0.10.0canton-libcrate at v0.11.0common,ledger,tokenorregistryv0.10.0failed to select a version for canton-api-clientcanton-api-client3.6.0-0.1.0The README tells users to pin all
canton-libcrates at the same tag. Those users must move their pins with this release, so the minor version signals that.How tested
cargo fmt -- --check,cargo clippy --all-targets --all-features -- -D warningsandcargo testpass locally.🤖 Generated with Claude Code