Skip to content

chore(deps): Update affinidi-tdk requirement from 0.12 to 0.14 - #30

Merged
stormer78 merged 2 commits into
mainfrom
dependabot/cargo/affinidi-tdk-0.14
Sep 19, 2026
Merged

stormer78 merged 2 commits into
mainfrom
dependabot/cargo/affinidi-tdk-0.14

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 19, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on affinidi-tdk to permit the latest version.

Changelog

Sourced from affinidi-tdk's changelog.

Changelog

All notable changes to this workspace are documented here. The format follows Keep a Changelog, and the workspace crates follow Semantic Versioning.

Per-crate version history is summarised here; for the full code history see git log.

[Unreleased]

Added

  • affinidi-net-guard 0.1.0: one egress guard for URLs an attacker can influence. affinidi-did-web 0.1.5, affinidi-tdk-common 0.6.11.

    A DID names the host a resolver fetches from, and a DID document names the endpoints a client dials, so each is a server-side request forgery primitive unless something refuses internal targets. affinidi-did-web 0.1.4 had the strongest guard in the stack, but it was private to a DID-method crate. It is now a leaf crate under crates/core/ with no affinidi-* dependency, so DID-method crates and external clients can take it without a cycle (ADR 0006).

    The crate enforces two halves, and both are needed. EgressPolicy::vet checks the scheme, userinfo, port, allow-list, special-use names and IP literals; reqwest never consults a resolver for a literal, so this is the only check a literal meets. GuardedResolver checks every address a name resolves to, fails the name on any blocked answer, and pins the connection to the vetted addresses. GuardedClient runs both, with no proxy, finite timeouts, no redirects by default and a capped body read.

    conformance/egress-vectors.v1.json is the vector file the TypeScript and Swift guards will share; the crate's tests run it, including DNS rebinding and redirect cases against local TLS listeners.

    affinidi-did-web now takes its address classification and resolver from the new crate, with its API and name set unchanged. The shared classifier also refuses some non-routable ranges that 0.1.4 accepted; its changelog lists them. affinidi-tdk-common adds create_guarded_http_client(extra_roots, &policy) on the existing platform TLS setup, and re-exports the crate as net_guard.

Changed

  • trust-tasks-rs 0.19 → 0.20 across the messaging family (breaking). affinidi-messaging-sdk 0.24.0, affinidi-messaging-didcomm-service 0.8.0, affinidi-messaging-mediator 0.24.0, affinidi-messaging-test-mediator 0.7.0, affinidi-tdk 0.14.0.

... (truncated)

Commits
  • 7d1be24 chore(deps)!: trust-tasks-rs 0.19 -> 0.20 across the messaging family (#786)
  • 89b5c1a fix(deny): allow Unicode-3.0 for the four ICU crates textwrap pulls in (#787)
  • a85b2df fix: a service endpoint's URI, and tsp reaching the messaging SDK (#785)
  • c736709 chore(deps)!: trust-tasks-rs 0.18 -> 0.19 across the messaging family (#784)
  • 086f5a7 feat: answer management Trust Tasks over TSP, not just DIDComm (#783)
  • da23170 feat: relay over WebSocket with a per-frame acknowledgement (#782)
  • 2b4c0d6 docs: a multi-mediator guide, and the gaps writing it exposed (#781)
  • 118f7bb ci: take coverage off the pull-request path (#780)
  • 2b728f4 refactor(bbs): take the curve stack from bls12_381_plus's re-exports (#778)
  • 7f47aa1 chore(deps): move to the RustCrypto digest 0.11 generation (#777)
  • Additional commits viewable in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 19, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner September 19, 2026 11:12
@dependabot dependabot Bot added rust Pull requests that update rust code dependencies Pull requests that update a dependency file labels Sep 19, 2026
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>
@stormer78
stormer78 merged commit 9d608e8 into main Sep 19, 2026
7 checks passed
@stormer78
stormer78 deleted the dependabot/cargo/affinidi-tdk-0.14 branch September 19, 2026 16:27
@stormer78 stormer78 mentioned this pull request Sep 22, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant