chore: pin canton-lib to v0.6.1, bump cbtc to 0.6.3 - #61
Merged
Conversation
Re-points the canton-lib deps (in both `cbtc` and `cbtc-tui`) from the temporary dev revision (c048dd7) to the released tag v0.6.1, now that the allocation client support is on a tagged canton-lib release. Bumps the cbtc crate version 0.6.2 -> 0.6.3.
There was a problem hiding this comment.
Pull request overview
Re-pins this workspace from a temporary canton-lib git rev to the tagged canton-lib v0.6.1 release, and bumps the cbtc crate version to 0.6.3. This is a dependency/packaging patch release with no functional code changes.
Changes:
- Update
canton-libgit dependencies fromrev = ...totag = "v0.6.1"in the root crate and the TUI crate. - Bump
cbtcversion0.6.2→0.6.3. - Regenerate
Cargo.lockto reflect the new tag-based sources and versions.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
cbtc-tui/Cargo.toml |
Re-pin canton-lib dependencies to tag = "v0.6.1" for the TUI crate. |
Cargo.toml |
Bump cbtc version and re-pin canton-lib dependencies to tag = "v0.6.1". |
Cargo.lock |
Lockfile regeneration reflecting cbtc 0.6.3 and canton-lib v0.6.1 sources. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
schronck
approved these changes
Jun 24, 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
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 release that re-pins cbtc-lib off the temporary canton-lib dev revision
and onto the tagged v0.6.1 release (which ships the allocation/DvP client
support), and bumps the cbtc crate to 0.6.3. No code changes.
Cargo.toml/cbtc-tui/Cargo.toml: the four canton-lib deps(
ledger/keycloak/registry/common) move fromrev = "c048dd7…"totag = "v0.6.1"— in both thecbtccrate and thecbtc-tuiworkspace member, so the workspace links a single canton-lib version.Cargo.toml:cbtcversion0.6.2→0.6.3.Cargo.lock: regenerated; canton-lib sources now resolve totag=v0.6.1#a9fd267.Follow-up to #59 (the allocation client PR, which used the rev pin while
canton-lib#23 was unreleased) and DLC-link/canton-lib#24 (the v0.6.1 release).
Testing
cargo check --workspaceclean against v0.6.1 (the tagged code is identical tothe dev rev plus the version bump, so behavior is unchanged).