fix(deps): bump dependency @posthog/mcp to ^0.10.0 - #94
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/posthog-mcp-0.x
branch
2 times, most recently
from
July 27, 2026 15:13
9f2495a to
fd8161c
Compare
renovate
Bot
force-pushed
the
renovate/posthog-mcp-0.x
branch
from
July 27, 2026 18:07
fd8161c to
9fd23c8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.9.1→^0.10.0Release Notes
PostHog/posthog-js (@posthog/mcp)
v0.10.1Compare Source
Patch Changes
23ce761Thanks @gesh! - Read the MCP client name/version and protocol version from each request's_meta(io.modelcontextprotocol/clientInfoandio.modelcontextprotocol/protocolVersion), so$mcp_client_name,$mcp_client_version, and$mcp_protocol_versionkeep populating under the MCP 2026-07-28 stateless revision, which removes theinitializehandshake. Existing clients are unaffected — when_metais absent, the values from the session token /initializestill apply.(2026-07-27)
v0.10.0Compare Source
Minor Changes
#4210
e732595Thanks @gesh! - feat(mcp): capture the negotiated MCP protocol version as$mcp_protocol_versionThe SDK now stamps
$mcp_protocol_version— the MCP spec version negotiated atinitialize(read off the server's initialize response) — on the$mcp_initializeevent and on every subsequent event for the session (tool calls, listings, and the$exceptionsibling). It's persisted in per-server session info and, on stateless / multi-pod deployments, recovered on other pods from the session token, which now carries the client's requested version in a newpvfield. Use it to track MCP spec-revision adoption and to break event metrics (error rate, latency) down by spec version.SessionTokenPayloadgains an optionalprotocolVersion, andPostHogMCP.captureInitializeaccepts an optionalprotocolVersion. (2026-07-21) (2026-07-22)Configuration
📅 Schedule: (in timezone UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.