Skip to content

chore(deps): pin canton-lib 0.10.0 - #4

Merged
hubagaspar91 merged 2 commits into
mainfrom
chore/deps/canton-lib-0.10.0
Oct 6, 2026
Merged

hubagaspar91 merged 2 commits into
mainfrom
chore/deps/canton-lib-0.10.0

Conversation

@hubagaspar91

Copy link
Copy Markdown
Collaborator

What

This PR pins canton-lib 0.10.0 in place of 0.9.0. The five canton-lib crates (common, ledger, registry, token, keycloak) move to tag v0.10.0. Cargo.lock changes only those five packages.

Why

Canton 3.6.1 rejects the top-level filter and verbose request fields with DEPRECATED_API_DISABLED, and Canton 3.7 removes them. canton-lib 0.10.0 sends eventFormat and updateFormat in their place. The active-contract queries and the update streams use these fields, so almost every read in this crate depends on the change. The first public release of this crate must work on Canton 3.6.1.

Effect on this crate

  • The crate's own code calls none of the items that canton-lib removes or renames, so no source file changes.
  • The ledger re-export no longer has submit::wait_for_transaction_tree or common::TransactionFilter. 0.1.0 is the first release, so no integrator depends on them.
  • canton-api-client stays at 3.6.0-0.1.0.

How it was tested

  • cargo fmt -- --check, cargo clippy --all-targets --all-features -- -D warnings and cargo test pass (114 tests).
  • cargo deny check advisories reports advisories ok.
  • The localnet suite passes on the sandbox. It lists deposit accounts, withdraw accounts, withdraw requests, holdings, credentials and credential offers, so it sends the new request format.
  • All 30 examples ran on devnet and passed, with the same small amounts as the earlier devnet round:
    • Reads: check_dars for both assets, check_balance for both assets, token_client, both offer lists, the CBTC deposit and withdraw account lists, and one poll of cbtc_check_withdraw_requests.
    • Flows: credentials, mint and redeem for CBTC and BETH, and cbtc_test_burn.
    • Token Standard writes: send, accept, reject, cancel, stream, allocate, withdraw allocation, split, consolidate and the four batch examples.

Follow-up

PR #3 pins canton-lib v0.9.0 in its README install section. After this PR merges, PR #3 gets one commit that moves that line to v0.10.0 and adds a CHANGELOG line.

🤖 Generated with Claude Code

canton-lib 0.10.0 sends eventFormat and updateFormat to the Ledger
API. Canton 3.6.1 rejects the filter and verbose fields that 0.9.0
sent. This crate calls none of the items that 0.10.0 removes, so
only the five tags and the lock file change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

The unrelated tempfile/getrandom lockfile change should be reverted.

Review effort: Balanced
Findings: None

What changed in this PR

Pins all five canton-lib crates to v0.10.0 for Canton 3.6.1 compatibility.

Changes:

  • Updates canton-lib dependencies from v0.9.0 to v0.10.0.
  • Refreshes corresponding lockfile entries.
File Description
Cargo.toml Updates five canton-lib dependency tags.
Cargo.lock Locks updated revisions and changes one unrelated resolution.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

The canton-lib update also moved tempfile to getrandom 0.4.3. That
change is not related to canton-lib, so the lock keeps the version
that main uses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hubagaspar91

Copy link
Copy Markdown
Collaborator Author

Reverted in fee7bbf. The canton-lib update also moved tempfile to getrandom 0.4.3. The lock now changes only the five canton-lib packages. Clippy and the tests pass with --locked.

@hubagaspar91
hubagaspar91 merged commit b88d95a into main Oct 6, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants