Skip to content

chore(deps): bump agent-client-protocol from 2.2.0 to 3.1.0 - #604

Merged
patchwave[bot] merged 3 commits into
mainfrom
dependabot/cargo/agent-client-protocol-3.1.0
Oct 15, 2026
Merged

patchwave[bot] merged 3 commits into
mainfrom
dependabot/cargo/agent-client-protocol-3.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 14, 2026

Copy link
Copy Markdown
Contributor

Bumps agent-client-protocol from 2.2.0 to 3.1.0.

Release notes

Sourced from agent-client-protocol's releases.

agent-client-protocol-rmcp-v3.1.0

Added

  • (unstable-v2) Add runnable v2 quickstart examples (#330)

agent-client-protocol-conductor-v3.1.0

Added

  • (acp) [breaking] make native transports and schema support opt-in (#397)
  • (acp) [breaking] adopt request-scoped MCP binding (#388)
  • (deps) bump the minor group with 14 updates (#381)
  • (rmcp) [breaking] upgrade integration to rmcp 3.4

Fixed

  • avoid sensitive transport logs and redact trace URL credentials (#401)
  • (polyfill) bound request-scoped HTTP resources (#389)
  • (acp) [breaking] preserve connection lifetimes and graceful drain (#385)
  • (acp) [breaking] preserve protocol-neutral raw JSON-RPC errors (#384)

Other

  • omit peer-controlled HTTP responses from test failure logs (#405)
  • prepare v3 package metadata and release guidance (#404)
  • slim dependency features and CI validation (#399)

Changed

  • Keep the Tokio/futures compatibility adapter in dev dependencies and omit unused futures executor and JSON logging features from production dependencies.
  • Request JSON Schema generation and rmcp's native MCP-over-ACP attachment support explicitly for integration tests. Enable the polyfill's draft-v2 support only with unstable_protocol_v2; test utilities no longer implicitly enable unrelated unstable protocol features.

Fixed

  • Redact HTTP URL userinfo and recognized credential query values in trace copies, including encoded keys and repeated parameters. Preserve explicit message recordings and original transport messages.
  • Trace inner MCP errors separately from outer ACP binding failures and redact HTTP declaration credentials without modifying transport messages.
  • Retain raw JSON-RPC error codes, omitted/null data, and error extension fields in traced response payloads. Trace method and parameter normalization is unchanged.

agent-client-protocol-cookbook-v3.1.0

Added

  • (acp) add prepared requests with preselected response handling (#407)

... (truncated)

Commits
  • 3f042ac chore: release (#406)
  • e7e3750 feat(acp): add prepared requests with preselected response handling (#407)
  • 9821e73 chore: release (#382)
  • 0dbd019 fix(http)!: honor custom configuration with safe WebSocket handshakes (#333)
  • 5eb8e9f test: omit peer-controlled HTTP responses from test failure logs (#405)
  • f07f48c docs: prepare v3 package metadata and release guidance (#404)
  • 1922272 fix: avoid sensitive transport logs and redact trace URL credentials (#401)
  • 0ff31d2 feat(acp): forward unstable subagents schema support (#402)
  • f80084c feat(config)!: make public configuration APIs extensible (#403)
  • 2e27638 fix(acp): allow singleton role IDs without Default (#400)
  • 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 2.2.0 to 3.1.0.
- [Release notes](https://github.com/agentclientprotocol/rust-sdk/releases)
- [Commits](agentclientprotocol/rust-sdk@agent-client-protocol-http-v2.2.0...agent-client-protocol-http-v3.1.0)

---
updated-dependencies:
- dependency-name: agent-client-protocol
  dependency-version: 3.1.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 Oct 14, 2026
@patchwave

patchwave Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

This PR is safe to merge

✅ Safe to merge (1)
Dependency Update
agent-client-protocol 2.2.0 → 3.1.0

View the full report · Analyzed by PatchWave

patchwave Bot added 2 commits October 14, 2026 16:44
ACP 3.1 disables schema generation and native process/stdio transports by default. Opt each feature in only for the crate that uses it so existing schema derives and ACP transports remain available.

[dependabot skip]

Generated-by: PatchWave (https://patchwave.ai)
PatchWave-Operation: fix
[dependabot skip]

Generated-by: PatchWave (https://patchwave.ai)
PatchWave-Operation: branch_update
@patchwave
patchwave Bot merged commit 4c7680f into main Oct 15, 2026
16 checks passed
@patchwave
patchwave Bot deleted the dependabot/cargo/agent-client-protocol-3.1.0 branch October 15, 2026 16:26
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