chore(deps): update to affinidi-tdk 0.8 + vta-sdk 0.17#128
Merged
Conversation
Bumps the affinidi ecosystem to the latest releases (vta-sdk 0.12 -> 0.17,
affinidi-tdk 0.7 -> 0.8.3, affinidi-did-common 0.3.5 -> 0.3.7, plus the rest
of the stack via cargo update).
The bump tightens several did-common wire types to `#[non_exhaustive]`, so the
old struct-literal construction in openvtc-core no longer compiles. Migrate to
the builders did-common now provides (behaviour identical — same fields set):
- VerificationMethod { .. } -> VerificationMethodBuilder::from_urls(..)
.properties(..).build() (3 sites in create_initial_webvh_did)
- Service { .. } -> ServiceBuilder::new(..).id_url(..).build()
- mediator_from_document's `Endpoint` match gains a `_ => None` arm
(Endpoint is now `#[non_exhaustive]`)
Production code resolves vta-sdk 0.17.0; the older 0.12/0.16 entries remain
only via dev-dependencies (the git-pinned VTI test harness and
messaging-test-mediator), not in shipped code.
Verified: cargo build --all-targets clean; workspace lib tests green
(openvtc-core 197, did-git-sign 46, 0 failures).
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
1 participant
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
Updates the affinidi dependency stack to the latest releases and migrates the
code to the API changes the bump brings.
vta-sdk0.12 → 0.17affinidi-tdk0.7 → 0.8.3affinidi-did-common0.3.5 → 0.3.7 (+ the rest of the stack viacargo update)Why the code change
The new releases tighten several
did-commonwire types to#[non_exhaustive],which forbids downstream struct-literal construction and exhaustive
match. Theexisting DID-document construction in
openvtc-coreno longer compiles, so it'smigrated to the builders
did-commonnow provides (behaviour is identical — thebuilders set the same fields):
VerificationMethod { .. }→VerificationMethodBuilder::from_urls(..).properties(..).build()(3 sites increate_initial_webvh_did)Service { .. }→ServiceBuilder::new(..).id_url(..).build()mediator_from_document'sEndpointmatch gains a_ => Nonearm (Endpointis now#[non_exhaustive])Notes
vta-sdk 0.17.0. The older0.12/0.16entries that remain in
Cargo.lockcome only through dev-dependencies(the git-pinned VTI test harness and
messaging-test-mediator), not shipped code.verifiable-trust-infrastructure(rev
82097382, vta-sdk 0.12.0) used for integration tests is left untouched —bumping it pulls a newer VTA test harness with its own potential breakage and
is a separate decision.
Test plan
cargo build --all-targets— clean (lib, bins, tests/dev-deps)cargo test --workspace --lib— green (openvtc-core 197, did-git-sign 46, 0 failures)cargo fmt