Skip to content

chore(deps): take affinidi-messaging-didcomm-service 0.12.1 and affinidi-tdk 0.17 - #33

Merged
stormer78 merged 1 commit into
mainfrom
chore/tdk-0-15-9
Sep 25, 2026
Merged

stormer78 merged 1 commit into
mainfrom
chore/tdk-0-15-9

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

Picks up the fixed Affinidi messaging crates.

crate before after
affinidi-messaging-didcomm-service 0.11.0 0.12.1 (requirement 0.12.1)
affinidi-messaging-sdk (transitive) 0.26.10 0.27.2
affinidi-messaging-didcomm (transitive) 0.15.8 0.15.9
affinidi-tdk 0.16.0 0.17.0 (requirement 0.17)
trust-tasks-rs 0.21.3 0.22.7 (requirement 0.22.7)

affinidi-messaging-didcomm-service 0.12 is built on messaging-sdk 0.27 / tdk 0.17 / trust-tasks-rs 0.22, so the tdk and trust-tasks-rs requirements move with it to keep one copy of each in the graph (cargo tree -d lists none of them). The 0.26 SDK line is not usable with affinidi-messaging-didcomm 0.15.9, so staying on it was not an option.

No source change. Dependency-only so the open draft (#32) rebases easily.

Checked locally: cargo fmt --all -- --check, cargo clippy --all-targets -- -D warnings, cargo test --all-targets (all pass).

…idi-tdk 0.17

Picks up the fixed Affinidi messaging crates: affinidi-messaging-didcomm-service 0.12.1, affinidi-messaging-sdk 0.27.2 and affinidi-messaging-didcomm 0.15.9. didcomm-service 0.12 is built on messaging-sdk 0.27 / affinidi-tdk 0.17 / trust-tasks-rs 0.22, so affinidi-tdk moves 0.16 -> 0.17 and trust-tasks-rs 0.21.3 -> 0.22.7 with it (one copy of each in the graph). No source change.

Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
@stormer78
stormer78 marked this pull request as ready for review September 25, 2026 15:18
@stormer78
stormer78 merged commit 33bc805 into main Sep 25, 2026
3 checks passed
@stormer78
stormer78 deleted the chore/tdk-0-15-9 branch September 25, 2026 15:27
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.

1 participant