deps: bump zentinel-agent-protocol to 0.6 - #3
Merged
Conversation
Pinned "0.5", which resolves to 0.5.13 while current releases are 0.6.x. No source changes were needed. Verified against 0.6.24 with cargo build, cargo fmt --check, clippy with -D warnings, and the test suite.
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.
This repo pinned
zentinel-agent-protocol = "0.5", which resolves to 0.5.13 while current releases are 0.6.x — cargo reportsAdding zentinel-agent-protocol v0.5.13 (available: v0.6.24)on every build.No source changes were needed here. The one API break this bump carries is the crate-root
PROTOCOL_VERSIONexport, which disappeared between 0.5.11 and 0.5.13 and is what brokezentinel-agent-graphql-securitywhen it moved (zentinelproxy/zentinel-agent-graphql-security#3). This repo does not reference it.Verified locally against 0.6.24 — pinned explicitly with
cargo update --precise, since CI resolves fresh and takes the newest 0.6.x:cargo build,cargo fmt --check,cargo clippy --workspace --all-targets -- -D warnings, andcargo test --workspace(27 tests).One of 19 agent repos still on 0.5; all were verified individually rather than swept blind.