Skip to content

chore(deps): take the released vta-sdk 0.31 and drop the git patch #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stormer78 merged 1 commit into from
Aug 28, 2026
Merged

chore(deps): take the released vta-sdk 0.31 and drop the git patch #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
91 changes: 46 additions & 45 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

25 changes: 3 additions & 22 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,7 @@ path = "src/main.rs"
# already drive `vta/memory/*` through the generic Trust-Task dispatcher, which
# picks TSP > DIDComm > REST from what both DID documents advertise. Nothing
# here is transport-aware.
#
# `agent-connect` is not in a published vta-sdk yet — see the `[patch]` below.
vta-sdk = { version = "0.28", features = [
vta-sdk = { version = "0.31", features = [
"client",
"session",
"didcomm",
Expand All @@ -42,7 +40,7 @@ vta-sdk = { version = "0.28", features = [
# The ephemeral did:key -> ACL grant -> auto-rotate-on-first-connect flow that
# the mediator, PNM and did-hosting already share. `onboarding` pulls only
# vta-sdk's session machinery, which is already here.
vti-secrets = { version = "0.2", default-features = false, features = ["onboarding"] }
vti-secrets = { version = "0.3", default-features = false, features = ["onboarding"] }

rmcp = { version = "3", features = ["server", "transport-io", "macros", "schemars"] }
schemars = "1"
Expand All @@ -64,21 +62,4 @@ tempfile = "3"
# `test-loopback` answers the Trust-Task surface in-process, so the integration
# tests exercise the real payloads `memory_{put,list,delete}` build without a
# VTA, a mediator, or a socket. Additive and zero-cost outside tests.
vta-sdk = { version = "0.28", features = ["test-loopback"] }

# Temporary: `vta_sdk::agent_connect` — the four-rung connect ladder this binary
# and `vta-mcp` share — is merged to the VTI workspace's main (PR #1081) but
# crates.io is still on vta-sdk 0.28.0, which predates it. A git patch rather
# than a path patch so the repo builds for anyone who clones it, not only next
# to a local checkout.
#
# Pinned to the merge commit, not `branch = "main"`: main moves, and a patch
# that silently follows it turns an unrelated upstream change into a broken
# build here with nothing in this repo's history to explain it. (The original
# feature branch was pinned instead, and was deleted on merge — same failure,
# faster.)
#
# Delete this whole block once `agent_connect` ships in a released vta-sdk; the
# `version = "0.28"` requirement above is what will resolve then, unchanged.
[patch.crates-io]
vta-sdk = { git = "https://github.com/OpenVTC/verifiable-trust-infrastructure", rev = "061300a14270c135b45d1232bf8c05e2bb45750d" }
vta-sdk = { version = "0.31", features = ["test-loopback"] }
Loading