Release 1.14.0 - #750
Conversation
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 0 new, 2 changed, 0 removedBuild ID: 23b513d8ad1c1be04811de0d URL: https://www.apollographql.com/docs/deploy-preview/23b513d8ad1c1be04811de0d ✅ AI Style Review — No Issues FoundThe pull request does not have any style issues. Duration: 3620ms
|
There was a problem hiding this comment.
LGTM — mechanical release PR (1.13.0 → 1.14.0) generated by Knope.
Extended reasoning...
Overview
This is an automated release PR generated by Knope for version 1.14.0. It performs only mechanical updates: bumps the version string from 1.13.0 to 1.14.0 across Cargo.toml, Cargo.lock, server.json, the nix and Windows install scripts, and the docs install commands in run.mdx; consolidates the five staged changesets into a new 1.14.0 section in CHANGELOG.md; and deletes the now-consumed changeset files. No source code in crates/ is touched — the underlying features and fixes already landed via prior PRs (#744, #747, #748, #749).
Security risks
None introduced by this PR itself. The release does package previously-merged security-relevant work (the rmcp 1.6 bump for the DNS rebinding advisory GHSA-89vp-x53w-74fx and the auth-server URL normalization fix), but those changes were reviewed in their original PRs and are not modified here.
Level of scrutiny
Low. Release-cut PRs that are limited to version bumps and changelog consolidation follow a well-established pattern in this repo (every prior X.Y.Z tag shows the same shape), and the version strings are internally consistent across all six bumped locations.
Other factors
The bug hunting system found no issues. CI will catch any version-string mismatch via build/test, and the docs preview is already building. No outstanding reviewer comments need follow-up.
This PR was created by Knope. Merging it will create a new release
Features
Resolve signing algorithm when a JWK omits
alg- @DaleSeo #732Apollo MCP Server now infers the signing algorithm from the authorization server's discovery metadata when a JWK omits the
algfield, enabling support for providers like Azure AD B2C, Microsoft Entra ID, and AWS Cognito.Capture tool call arguments and results in OpenTelemetry spans - @DaleSeo #748
Tool execution spans now include
apollo.mcp.tool_argumentsandapollo.mcp.tool_resultattributes on thecall_toolspan, andapollo.mcp.graphql_queryandapollo.mcp.graphql_responseon the childexecutespan. This makes it possible to correlate traces in observability dashboards with the actual queries and data that triggered them.Expose
trace_idto theon_execute_graphql_operationRhai hook - @DaleSeo #745The
on_execute_graphql_operationRhai hook now exposes a read-onlyctx.trace_idproperty, allowing scripts to access the current OpenTelemetry trace ID for custom structured logging. The value is a 32-character lowercase hex string when an OpenTelemetry trace context is active and an empty string otherwise, matching the format already used for thetrace_id=<hex>prefix on server log lines. This makes it possible to emit log lines from Rhai withtrace_idas a discrete field that log aggregators (Splunk, ELK, etc.) can index for correlation with distributed traces.Fixes
Bump
rmcpto 1.6 to address DNS rebinding advisory - @DaleSeo #742Updates the
rmcpStreamable HTTP server transport to 1.6.0, which patches GHSA-89vp-x53w-74fx (CVE-2026-42559). Host header validation is now performed insidermcpitself, with atracing::warn!event on each rejection so log-based alerting on DNS rebinding attempts continues to work; the server's existingtransport.streamable_http.host_validationconfiguration is unchanged.Preserve raw authorization server URLs in protected-resource metadata - @DaleSeo #749
Apollo MCP Server no longer normalizes the
transport.auth.serversentries when it sets theauthorization_serversfield in/.well-known/oauth-protected-resource. Before, a scheme-authority-only configuration value, likehttps://auth.example.com, was re-parsed throughurl::Url, which added a trailing/to the empty path. This normalized form ended up in the metadata and caused mismatches in issuer claims for strict OAuth clients that compareauthorization_serverswith the auth server's discoveryissuer. Now, server URLs are passed through exactly as they are, so users need to make sure each entry matches their auth server'sissuerprecisely.