Skip to content

chore: bump agentrust-trace to >=0.4 (drop <0.4 workaround cap) #58

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
imran-siddique merged 1 commit into from
Jul 21, 2026
Merged

chore: bump agentrust-trace to >=0.4 (drop <0.4 workaround cap) #58

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
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- Bumped `agentrust-trace` to `>=0.4`. The previous `<0.4` cap worked around the
published 0.3.0 lacking the TRACE A2A `delegation` block that cA2A records
carry; 0.4.0 ships that block, so the cap is removed. cA2A still owns the
delegation-block semantics natively (`trace_binding`/`ca2a_verify.dag`); no
code shim was needed. All tests pass against 0.4.0.

### Added

- A2A transport adapter (`ca2a_runtime.transport`): parse/attach cA2A extension
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ dependencies = [
# TRACE record models + RFC 8785 signing, reused rather than reimplemented
# (see ROADMAP Tier 0). Pin a compatible minor; cross-repo skew is a known
# risk documented in LIMITATIONS.md.
"agentrust-trace>=0.3,<0.4",
"agentrust-trace>=0.4",
"rfc8785>=0.1",
]

Expand Down