Skip to content

chore(deps): take affinidi-did-resolver-cache-sdk 0.8.40 — a deactivated did:webvh no longer resolves - #2

Merged
stormer78 merged 1 commit into
mainfrom
chore/cache-sdk-0.8.39
Oct 1, 2026
Merged

stormer78 merged 1 commit into
mainfrom
chore/cache-sdk-0.8.39

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

Why

SEC-4045 / VGI-04. Up to affinidi-did-resolver-cache-sdk 0.8.38, resolving a did:webvh whose log ends in a deactivation entry returned the last DID document as Ok, keys and all. Anything that trusts a DID through the cache SDK therefore kept accepting a deactivated did:webvh. 0.8.39 (affinidi/affinidi-tdk-rs#907) makes that resolution fail, the same way a deactivated did:web (a 404) already did. did-scid 0.2.8 does the same for did:scid:vh.

This repo only reaches the crate transitively: demo/ (pcs-vetting-prototype) → vta-sdk → affinidi-did-resolver-cache-sdk. The library crate predicate-credential-system doesn't depend on it at all. origin/main had the lockfile at 0.8.38. A survey found nothing here that depends on a deactivated did:webvh resolving.

What

This only changes the lockfile: cargo update -p affinidi-did-resolver-cache-sdk -p did-scid, with no bare cargo update. No manifest names a cache-sdk floor, so this fixes what this repo builds. It doesn't change what downstream consumers resolve.

Lockfile changes (git diff Cargo.lock)

Package Before After
affinidi-did-resolver-cache-sdk 0.8.38 0.8.40
did-scid 0.2.7 0.2.8

No other packages moved. 0.8.40 is the newest release compatible with the MSRV (1.95). It is a clippy-only follow-up to 0.8.39 (a collapsible_if let-chain) with no behaviour change.

Verification

Run locally with the same commands as ci.yml, on stable (rustc 1.99.0) unless noted:

  • cargo fmt --all -- --check: passes
  • cargo clippy -p predicate-credential-system --all-targets --all-features -- -D warnings: passes
  • cargo test -p predicate-credential-system --all-features --all-targets: passes
  • cargo build -p predicate-credential-system --no-default-features: passes
  • RUSTDOCFLAGS="-D warnings" cargo doc --no-deps -p predicate-credential-system --features serde: passes
  • cargo +1.95.0 check -p predicate-credential-system --all-features (MSRV): passes
  • cargo package -p predicate-credential-system --locked: passes

CI doesn't cover demo/, which is the crate that actually uses the updated package, so I also ran:

  • cargo test -p pcs-vetting-prototype --locked: passes (14 tests)

Compatibility

There is no API change. The only behaviour change: a deactivated did:webvh / did:scid:vh now fails to resolve instead of returning its last document. The published library crate is unaffected because it doesn't depend on the resolver.

…ted did:webvh no longer resolves

Lockfile-only. affinidi-did-resolver-cache-sdk 0.8.38 -> 0.8.40 and
did-scid 0.2.7 -> 0.2.8, both reached transitively through vta-sdk
from demo/ (pcs-vetting-prototype).

Before cache-sdk 0.8.39 (affinidi/affinidi-tdk-rs#907) a did:webvh
whose log ends in a deactivation resolved Ok to its last DID document,
keys included; 0.8.39 makes that resolution fail, and did-scid 0.2.8
does the same for did:scid:vh. 0.8.40 is a clippy-only follow-up with
no behaviour change. Refs SEC-4045 / VGI-04.

Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
@stormer78
stormer78 merged commit 4be4598 into main Oct 1, 2026
8 checks passed
@stormer78
stormer78 deleted the chore/cache-sdk-0.8.39 branch October 1, 2026 14:50
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