Repository navigation
chore(deps): Update affinidi-tdk requirement from 0.12 to 0.14 - #30
Merged
Merged
Conversation
Updates the requirements on [affinidi-tdk](https://github.com/affinidi/affinidi-tdk-rs) to permit the latest version. - [Changelog](https://github.com/affinidi/affinidi-tdk-rs/blob/main/CHANGELOG.md) - [Commits](affinidi/affinidi-tdk-rs@affinidi-tdk-v0.12.0...affinidi-tdk-v0.14.0) --- updated-dependencies: - dependency-name: affinidi-tdk dependency-version: 0.14.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
0.14 does not build. `affinidi-messaging-core` 0.1.8 added `#[non_exhaustive]` to `Inbound`, and `affinidi-messaging-sdk` 0.24.0 - what affinidi-tdk 0.14 pulls in - constructs that struct with a struct expression in `transport_adapter.rs`. Its requirement is `affinidi-messaging-core = "0.1.6"`, so the caret range accepts 0.1.8 and the SDK stops compiling: `error[E0639]: cannot create non-exhaustive struct using struct expression`. Nothing in this repo can fix that from below. We have no Cargo.lock in git - this is a library, so CI resolves fresh on every run and always picks up 0.1.8. The only lever is the requirement itself. 0.16.0 moves to `affinidi-messaging-sdk` 0.26.10, which does not build `Inbound` by hand, and the three failing jobs go green. affinidi-tdk is a dev-dependency used by the examples and integration tests, so this changes nothing for a consumer of the published crate and needs no CHANGELOG entry. Every other dependency is already at the newest version its requirement allows, so no other manifest change was needed. Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
Merged
stormer78
added a commit
that referenced
this pull request
Sep 22, 2026
Cuts 0.11.0, the first published release since 0.9.1. 0.10.0 was merged and versioned but never tagged, so it never reached crates.io; 0.11.0 carries its changes together with the taskDigestMultibase work merged in #31. - Cargo.toml: 0.10.0 -> 0.11.0 - CHANGELOG.md: [Unreleased] moves under [0.11.0] - 2026-09-22, with an "Upgrading from 0.9" section for consumers crossing both releases at once; the [0.10.0] section is marked as never published - README.md: the upgrade-ordering table gains a 0.11.0 row and notes that 0.10.0 first ships in 0.11.0 No code changes. The affinidi-tdk 0.12 -> 0.16 bump (#30) is a dev-dependency only and is not user-visible. Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
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.
Updates the requirements on affinidi-tdk to permit the latest version.
Changelog
Sourced from affinidi-tdk's changelog.
... (truncated)
Commits
7d1be24chore(deps)!: trust-tasks-rs 0.19 -> 0.20 across the messaging family (#786)89b5c1afix(deny): allow Unicode-3.0 for the four ICU crates textwrap pulls in (#787)a85b2dffix: a service endpoint's URI, andtspreaching the messaging SDK (#785)c736709chore(deps)!: trust-tasks-rs 0.18 -> 0.19 across the messaging family (#784)086f5a7feat: answer management Trust Tasks over TSP, not just DIDComm (#783)da23170feat: relay over WebSocket with a per-frame acknowledgement (#782)2b4c0d6docs: a multi-mediator guide, and the gaps writing it exposed (#781)118f7bbci: take coverage off the pull-request path (#780)2b728f4refactor(bbs): take the curve stack from bls12_381_plus's re-exports (#778)7f47aa1chore(deps): move to the RustCrypto digest 0.11 generation (#777)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)