Skip to content

Commit d49400a

Browse files
committed
feat(mcp): declare posthog.mcp stable
What: a Versioning section in the posthog.mcp README and a release note saying the API and the $mcp_* event schema are stable from this release. Why: posthog.mcp now counts calls the same way as the spec and the other SDKs (posthog-python#1199), so it can make the stability promise sdk-specs#189 defines. It ships inside posthog 7.x, so there's no separate version bump. Tested: docs and release note only; no code change.
1 parent 8b1c0a0 commit d49400a

2 files changed

Lines changed: 9 additions & 0 deletions

File tree

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
pypi/posthog: minor
3+
---
4+
5+
`posthog.mcp` is now stable. From this release, a minor or patch release of `posthog` no longer makes breaking changes to the `posthog.mcp` API, renames or removes a `$mcp_*` event or property, changes its type, or changes which requests send an event, so your saved insights keep working across upgrades. New events and properties can still arrive in minor releases. Upgrading needs no code change.

‎posthog/mcp/README.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,10 @@ Request headers use the same identity and package version, so SDK Health can com
3636
Because `$lib` is a client-level identity, `instrument()` relabels every event sent by the client passed to it.
3737
Use a client dedicated to MCP analytics if the application also captures unrelated events.
3838

39+
## Versioning
40+
41+
`posthog.mcp` is stable. It ships inside the `posthog` package, so it follows that package's version rather than its own. A minor or patch release of `posthog` doesn't change the `posthog.mcp` API in a breaking way, and doesn't rename or remove a `$mcp_*` event or property, change its type, or change which requests send an event, so saved insights keep working across upgrades. It may add events and properties, and redact more of a captured value. The rules come from the [MCP analytics spec](https://github.com/PostHog/sdk-specs/blob/main/openspec/specs/mcp-analytics/spec.md), section "Event schema stability".
42+
3943
## Defaults and opt-outs
4044

4145
A valid echoed conversation handle takes precedence over transport sessions. A request that already carries a transport session or a PostHog session token does not mint a new handle or append a prompt-back block. Requests carrying neither use the conversation fallback.

0 commit comments

Comments
 (0)