chore: release

[acp-release-bot]

🤖 New release

• agent-client-protocol-derive: 3.3.0 -> 3.4.0
• agent-client-protocol: 3.3.0 -> 3.4.0 (✓ API compatible changes)
• agent-client-protocol-polyfill: 3.3.0 -> 3.4.0 (✓ API compatible changes)
• agent-client-protocol-trace-viewer: 3.3.0 -> 3.4.0 (✓ API compatible changes)
• agent-client-protocol-conductor: 3.3.0 -> 3.4.0 (✓ API compatible changes)
• agent-client-protocol-http: 3.3.0 -> 3.4.0
• agent-client-protocol-cookbook: 3.3.0 -> 3.4.0 (✓ API compatible changes)
• agent-client-protocol-rmcp: 4.0.3 -> 4.0.4

Changelog

agent-client-protocol-derive

3.0.0 - 2026-10-06

Other

• prepare v3 package metadata and release guidance (#404)

agent-client-protocol

3.4.0 - 2026-10-16

Added

• (acp) update schema to 1.12.0 and align v2 lifecycle (#423)

Fixed

• (acp) align protocol version negotiation (#424)

agent-client-protocol-polyfill

3.4.0 - 2026-10-16

Fixed

• (deps) upgrade hmac and sha2 together (#422)

agent-client-protocol-trace-viewer

3.4.0 - 2026-10-16

Other

• update Cargo.lock dependencies

agent-client-protocol-conductor

3.4.0 - 2026-10-16

Fixed

• (acp) align protocol version negotiation (#424)

agent-client-protocol-http

3.0.0 - 2026-10-06

Added

• (config) [breaking] make public configuration APIs extensible (#403)

Fixed

• (http) [breaking] honor custom configuration with safe WebSocket handshakes (#333)
• avoid sensitive transport logs and redact trace URL credentials (#401)
• (http) gracefully finish client transports after builder completion (#396)
• (acp) [breaking] preserve connection lifetimes and graceful drain (#385)
• (acp) [breaking] preserve protocol-neutral raw JSON-RPC errors (#384)

Other

• prepare v3 package metadata and release guidance (#404)
• slim dependency features and CI validation (#399)

Breaking changes

• WebSocket URLs passed to HttpClient::with_client or
  with_endpoint_and_client now return WebSocketRequiresBuilder before network
  I/O. Migrate to builder(...).configure_http(...).build() or
  builder_with_endpoint(...) so the transport can enforce connection policies.
  See the
  migration guide.
• Unconfigured WebSockets now share reqwest's proxy discovery and TLS verification
  defaults, replacing direct connections and bundled WebPKI roots. Environment
  proxies, enabled system-proxy discovery, and platform certificate verification
  can change routing and trust. Use no_proxy() and explicit tls_certs_only
  roots when those defaults are not appropriate.

Deprecated

• Retain HttpClient::with_client and with_endpoint_and_client as deprecated
  HTTP/SSE compatibility wrappers with unchanged path handling.
  from_http_client(exact_endpoint, client) preserves shared reqwest clients for
  HTTP/SSE; its endpoint is exact and does not append /acp.

Changed

• Document the caller constraint against setting reserved WebSocket handshake
  headers through reqwest::Proxy::headers. Plain-WS proxy headers can overwrite
  SDK request headers after assembly; opaque proxy configuration cannot be
  inspected or rejected at build time. Cover normal plain-WS proxy headers and
  fail-closed accept validation after a proxy key override.
• Breaking: make ServerOptions and CorsOptions non-exhaustive.
  Replace server option literals (including struct update syntax) with
  ServerOptions::default().with_path(...).with_cors(...).with_health_endpoint(...);
  existing fields remain public. Downstream CORS matches need a wildcard arm.
  Defaults and runtime policies are unchanged. See the
  config API migration guide.
• Limit Axum to HTTP1/Tokio, WebSockets, and tracing/tower-log observability.
  Remove unused Axum macros and extractors; JSON extraction is enabled only for
  tests. Drop unused test-utility and tracing-subscriber dev dependencies and
  the unused production futures executor feature.
• Adapt HttpClient's ConnectTo conversion to the core SDK's breaking
  optional ConnectionDriver return type. Channels and HTTP framing remain
  unchanged; no new resource limits are introduced.

Fixed

• Apply custom headers, TLS, proxies, DNS, and timeouts to WebSocket handshakes.
  Enforce HTTP/1.1 and disable redirects for WebSockets without changing HTTP/SSE
  policies. Validate the upgrade response before sending queued ACP data, and
  reject unsupported subprotocols and extensions.
• Replace HTTP POST, SSE, and WebSocket payload diagnostics with bounded
  metadata. Do not log peer-controlled IDs, close reasons, or transport error
  text (which may include credentials or message content).
• Cooperatively finish HTTP client connections created through the public builder:
  drain accepted ordered POSTs and WebSocket frames before physical cleanup, reject
  output from escaped transport senders, and report transport failures during shutdown.
• Preserve raw JSON-RPC error codes, omitted versus null data, and error
  extension fields across HTTP/SSE and WebSocket transports, using the core
  SDK's new RawJsonRpcResponse representation.
• Preserve HTTP channel pumps when an agent-factory endpoint has no owned
  driver; absence is not agent completion while its transport remains open.
• On active agent completion, reject further output from escaped sender clones
  and drain accepted frames before removing the connection and closing its
  streams, without waiting for those clones to be dropped.
• Keep router cancellation owned while natural cleanup awaits its drain.
  Explicit shutdown no longer detaches a taken router task or retains the
  connection through that orphaned task.

agent-client-protocol-cookbook

3.4.0 - 2026-10-16

Added

• (acp) update schema to 1.12.0 and align v2 lifecycle (#423)

agent-client-protocol-rmcp

4.0.4 - 2026-10-16

Other

• updated the following local packages: agent-client-protocol

---

This PR was generated with release-plz.