Repository navigation
fix: move onto the v2 SDK and protocol - #3
Merged
Merged
Conversation
CI has been red because this is the one agent repo taking zentinel-agent-sdk from crates.io, where the only release was 0.2.0 — code targeting the v1 protocol removed in 26.02. That release cannot compile against any current zentinel-agent-protocol. Bumps to the freshly published zentinel-agent-sdk 0.3.0 and protocol 0.6. The dependency bump alone is not enough: this agent also referenced zentinel_agent_protocol::PROTOCOL_VERSION, a crate-root export that no longer exists. The v2 equivalent is v2::PROTOCOL_VERSION_2, which the rest of this file already imports from. Same value (2), same wire behaviour.
This was referenced Aug 21, 2026
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
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.
Turns this repo's CI green again. It has been red because it is the one agent repo taking
zentinel-agent-sdkfrom crates.io rather than a path dependency, and the only published release was 0.2.0 — code targeting the v1 protocol removed in 26.02, which cannot compile against any currentzentinel-agent-protocol.zentinel-agent-sdk 0.3.0is now published (zentinelproxy/zentinel-agent-rust-sdk#3), so this bumps to it, along withzentinel-agent-protocol0.5→0.6.The dependency bump alone was not enough
This agent also referenced
zentinel_agent_protocol::PROTOCOL_VERSION— a crate-root export that no longer exists. It was reachable in protocol 0.5.11 (what the old lockfile resolved) but is not re-exported at the root in 0.5.13 or 0.6.x.The v2 equivalent is
v2::PROTOCOL_VERSION_2, which this same file already imports its other v2 types from. Same value (2), so no wire-behaviour change — 4 call sites inAgentResponse { version: … }.Worth noting for anyone hitting the same thing: the other five agent repos using the SDK take it as a path dependency, so they never saw this.
Verification
Built against the published 0.3.0 (not a local patch):
cargo fmt --check,cargo clippy --workspace --all-targets -- -D warnings, andcargo test --workspace(71 passed) all clean.Once this lands, #2 (the README install-path fix, parked behind this) can merge too.