chore: release v1.8.0

[github-actions]

🤖 New release

• rmcp-macros: 1.7.0 -> 1.8.0
• rmcp: 1.7.0 -> 1.8.0

Changelog

rmcp-macros

1.8.0 - 2026-06-22

Added

• deprecate roots, sampling, and logging (SEP-2577) (#884)

Fixed

• strip and validate tool outputSchema and inputSchema (#860)
• remove unnecessary fields from tools' inputSchema (#856)

Other

• refine mcpmate listing copy (#885)
• added jilebi-mcp to the list of built with rmcp (#861)

rmcp

1.8.0 - 2026-06-22

Added

• standardize resource-not-found error code (SEP-2164) (#899)
• validate OAuth authorization response issuer (#896)
• specify OIDC application_type during dynamic client registration (SEP-837) (#883)
• deprecate roots, sampling, and logging (SEP-2577) (#884)

Fixed

• (auth) preserve configured reqwest client (#917)
• (auth) align OAuth metadata discovery ordering (#887)
• align progress timeout token (#909)
• (elicitation) preserve enumNames through ElicitationSchema serde round-trip (#905)
• return tool errors for invalid arguments (#894)
• (auth) apply offline_access to reauth paths (#897)
• update peer info on duplicate initialize (#862)
• strip and validate tool outputSchema and inputSchema (#860)
• remove unnecessary fields from tools' inputSchema (#856)
• reject init header/body version mismatch (#853)
• align protocol version negotiation (#855)
• accept 200 with empty body in response to notifications in addition to 202 (#849)

Other

• Allow custom HTTP clients for OAuth (#908)
• Add progress-aware request timeout reset (#858)
• (server) document Err vs Ok(CallToolResult::error) visibility contract on ServerHandler::call_tool (#854)
• refine mcpmate listing copy (#885)
• added jilebi-mcp to the list of built with rmcp (#861)

---

This PR was generated with release-plz.

[joshuajbouw]

Just a note that this release had broken the public API by changing Peer::peer_info() to return Option<Arc<InitializeResult>> instead of Option<&InitializeResult>. Resulting in our CI and builds to break even though it was set as 1.7. Cargo tends to take the everything above 1.7 through to 2.0. Please be careful 👍🏻 .

A CI with cargo-public-api check would be recommended.

[DaleSeo]

Thanks for bringing this up, @joshuajbouw. I'm sorry about the issue.

We do run cargo-semver-checks in CI, but it didn't seem to detect this class of breaking change yet per obi1kenobi/cargo-semver-checks#5

We've added a breaking-change warning to the release notes to help reduce confusion. I also opened #924 to add a cargo-public-api diff check to CI, which will cover that gap and ensure these changes are reviewed and version-bumped intentionally.

I really appreciate you taking the time to help us improve this. 🙏

[joshuajbouw]

Awesome! Good work @DaleSeo, much appreciated!