You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer whose code calls Mixpanel, I want patch-it to know when Mixpanel breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
Find Mixpanel's sources and record them with the date checked (verify, don't guess; leave TBD if unknown):
deprecations / sunset page
API changelog (RSS / Atom if there is one)
OpenAPI spec, if published
official SDKs and their release notes / changelogs (Python and JS first)
API versioning scheme (date-based, path, header, none)
Pick the format plugin for each source (OpenAPI, RSS, GitHub Releases, changelog file, registry, prose) and add catalog lines
Golden test: a saved copy of each source in, the expected events out
One real historical breaking change as a replay fixture
Provider page providers/mixpanel.md from the template
Add or update its row in docs/plugins.md (see CONTRIBUTING.md)
Note what the client needs to fix it (existing handler, or a new fix kind in the client)
Acceptance criteria
Daily ingest emits Mixpanel events, each with source_url and an exact source_excerpt
The replayed historical change produces the right events
The provider page lists every source with its date checked
Research findings (checked 2026-11-19): no spec plugin; a deprecated-pages reader is the next step
Sources
Item
Finding
Deprecations / sunset page
None (/docs/deprecations is a 404). Deprecations are prose on their own reference pages, which the docs index (llms.txt) marks [Deprecated]: Project Secret ("deprecated and will be fully retired on March 3, 2027"), the Data Pipelines API, request signatures.
Changelog
docs.mixpanel.com/changelogs. Its RSS (/changelogs/rss.xml) holds only the last 15 entries, titled with bare dates. The full source has 203 entries since 2022-03-29, mostly product features. A few API-level ones: TLS 1.0/1.1, "Retiring /decide Endpoint", the US-to-EU forwarding sunset.
OpenAPI
Hand-edited specs in mixpanel/docs (openapi/, since 2026-05-27) and the archived mixpanel/docs-legacy (2023-08 to 2026-06). Neither has tags, and neither has a license.
Mostly none: paths like /api/2.0, data-deletions/v3.0, Platform /v1. The beta Insights API uses a Mixpanel-Version: YYYY-MM-DD header.
Why no spec plugin
The specs never mark a deprecation, even for Mixpanel's real ones:
Over 114 spec commits (3.2 years), the openapi plugin's deprecations-only rule finds 0 events.
The removals aren't marked either. 12 operations were removed, none deprecated first, and all were documentation fixes (the gdpr path prefix moving around). The one real removal, Cloud Import (connectors.openapi.yaml, "Remove connectors API docs", #1607, 2024-11-08), was a deleted file. Its PR says the feature had been "deprecated for nearly two years", but the spec never marked it.
The deprecations Mixpanel did announce appear in no spec: Project Secret, Data Pipelines, /decide.
A plugin on the specs would stay silent through Mixpanel's next deprecation too. Listing it as supported would claim coverage that doesn't exist. There's also no real change to replay, and no license for saving the specs as test data.
Next step
A reader for the reference pages the docs index marks [Deprecated], citing a snapshot of each page. That's where Mixpanel actually announces deprecations, often with a date (Project Secret: 2027-03-03). It needs a new reader and a decision on what each page's subject is (an auth method, an API, an endpoint). Leaving this open in Backlog until then.
Activity
brandonphelps1212 commentedon Nov 19, 2026
Research findings (checked 2026-11-19): no spec plugin; a deprecated-pages reader is the next step
Sources
/docs/deprecationsis a 404). Deprecations are prose on their own reference pages, which the docs index (llms.txt) marks[Deprecated]: Project Secret ("deprecated and will be fully retired on March 3, 2027"), the Data Pipelines API, request signatures./changelogs/rss.xml) holds only the last 15 entries, titled with bare dates. The full source has 203 entries since 2022-03-29, mostly product features. A few API-level ones: TLS 1.0/1.1, "Retiring /decide Endpoint", the US-to-EU forwarding sunset.openapi/, since 2026-05-27) and the archived mixpanel/docs-legacy (2023-08 to 2026-06). Neither has tags, and neither has a license.CHANGELOG.md), mixpanel-js (Apache-2.0,CHANGELOG.md), mixpanel-node (MIT, releases only)./api/2.0,data-deletions/v3.0, Platform/v1. The beta Insights API uses aMixpanel-Version: YYYY-MM-DDheader.Why no spec plugin
The specs never mark a deprecation, even for Mixpanel's real ones:
openapiplugin's deprecations-only rule finds 0 events.connectors.openapi.yaml, "Remove connectors API docs", #1607, 2024-11-08), was a deleted file. Its PR says the feature had been "deprecated for nearly two years", but the spec never marked it./decide.A plugin on the specs would stay silent through Mixpanel's next deprecation too. Listing it as supported would claim coverage that doesn't exist. There's also no real change to replay, and no license for saving the specs as test data.
Next step
A reader for the reference pages the docs index marks
[Deprecated], citing a snapshot of each page. That's where Mixpanel actually announces deprecations, often with a date (Project Secret: 2027-03-03). It needs a new reader and a decision on what each page's subject is (an auth method, an API, an endpoint). Leaving this open in Backlog until then.