Skip to content

chore(deps): bump agent-client-protocol from 3.5.0 to 5.0.0 - #477

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/agent-client-protocol-5.0.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/agent-client-protocol-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026

Copy link
Copy Markdown
Contributor

Bumps agent-client-protocol from 3.5.0 to 5.0.0.

Release notes

Sourced from agent-client-protocol's releases.

agent-client-protocol-conductor-v5.0.0

Added

  • (acp) [breaking] adopt schema 1.15.0 and its proxy-chain types (#480)
  • (acp) [breaking] v1 connection type, SessionSetup, and the v5 migration guide (#472)
  • (acp) [breaking] version-neutral Builder::new and v1::schema / v2::schema (#470)
  • (rmcp) [breaking] move the rmcp integration behind a versioned rmcp_3 feature (#471)
  • (acp) [breaking] type request handle IDs by protocol version (#467)
  • (acp) [breaking] version-neutral raw JSON-RPC request IDs (#466)
  • (acp) [breaking] version-neutral SDK Error with conversions to v1 and v2 schema errors (#465)
  • (acp) negotiate proxy/initialize versions like initialize (#464)
  • (acp) [breaking] rename proxy methods to proxy/initialize and proxy/successor (#460)
  • (acp) [breaking] keep v1 independent of unstable_protocol_v2; version-agnostic conductor and proxies (#459)
  • (acp) [breaking] remove JSON-RPC batch support (#454)

Fixed

  • conform the conductor and proxies to the proxy-chains RFD cleanup (#2743) and default v2 entity cancel to -32602 (#482)
  • (conductor) [breaking] narrow the conductor API and fix multi-version chains (#475)
  • [breaking] narrow transport and MCP APIs and fix rmcp integration issues (#476)
  • (acp) [breaking] version-neutral wire envelopes and extensible proxy types (#478)
  • (acp) [breaking] v1 session stream reports prompt errors and full responses (#474)
  • (acp) reject proxy MCP server names that collide with the client's (#456)
  • remove redundant license-file metadata (#448)

Other

  • (acp) [breaking] reach each protocol version's schema only through v1::schema / v2::schema (#481)
  • prepare the 5.0 release (migration guide, stability policy, version pins) (#479)
  • (acp) [breaking] v1 and v2 modules with versioned entry points (#469)

agent-client-protocol-cookbook-v5.0.0

Added

  • (acp) [breaking] v1 connection type, SessionSetup, and the v5 migration guide (#472)
  • (acp) [breaking] version-neutral Builder::new and v1::schema / v2::schema (#470)
  • (rmcp) [breaking] move the rmcp integration behind a versioned rmcp_3 feature (#471)
  • (acp) [breaking] type request handle IDs by protocol version (#467)

Fixed

  • (acp) adopt schema 1.15.1 and agent-side permission cancellation in v2 (#487)
  • [breaking] narrow transport and MCP APIs and fix rmcp integration issues (#476)
  • (acp) [breaking] v1 session stream reports prompt errors and full responses (#474)
  • follow the remaining ACP schema 1.13 rules in Testy, examples, and docs (#452)
  • remove redundant license-file metadata (#448)

Other

  • (acp) [breaking] reach each protocol version's schema only through v1::schema / v2::schema (#481)

... (truncated)

Commits
  • 1b1399a chore: release v5.0.0 (#449)
  • ffbe51f fix(acp): adopt schema 1.15.1 and agent-side permission cancellation in v2 (#...
  • 2439628 fix(acp): negotiate a repeated initialize like the first one (#486)
  • 2596425 fix(acp): answer unhandled session requests and bound parked messages (#485)
  • 4912e08 fix(acp): don't let peer errors match the SDK's termination predicates (#484)
  • 39915a2 fix(http): only open session streams for sessions the connection knows (#483)
  • d13e36b fix: conform the conductor and proxies to the proxy-chains RFD cleanup (#2743...
  • 75e00be refactor(acp)!: reach each protocol version's schema only through v1::schema ...
  • ccd26a8 feat(acp)!: adopt schema 1.15.0 and its proxy-chain types (#480)
  • 602240b docs: prepare the 5.0 release (migration guide, stability policy, version pin...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [agent-client-protocol](https://github.com/agentclientprotocol/rust-sdk) from 3.5.0 to 5.0.0.
- [Release notes](https://github.com/agentclientprotocol/rust-sdk/releases)
- [Commits](agentclientprotocol/rust-sdk@agent-client-protocol-http-v3.5.0...agent-client-protocol-http-v5.0.0)

---
updated-dependencies:
- dependency-name: agent-client-protocol
  dependency-version: 5.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants