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 Amplitude, I want patch-it to know when Amplitude breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
Find Amplitude'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/amplitude.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 Amplitude 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): not yet, revisit at the Developer API's first deprecation or 1.0
Sources
Item
Finding
Deprecations / sunset page
None for APIs. SDK maintenance and support states a lifecycle policy (Beta, GA, Maintenance for at least 12 months, End of life), with no dates per SDK.
Changelog
amplitude.com/releases, RSS at /releases/feed.xml. It's a product changelog with a rolling 200 items. 2 items match deprecation words: one deprecates MCP tools, not an API, and one is a "No" answer.
OpenAPI
Only for the new Developer API: openapi/bundled/openapi.bundled.yaml in amplitude/developer-cli, tags developer-cli-v0.2.0 to v0.7.0, since 2026-06. The repo is MIT, but the spec's own info.license says "Proprietary". The classic APIs (HTTP V2, Batch, Export, Dashboard REST) have no published spec.
SDKs
Amplitude-Python, Amplitude-TypeScript (@amplitude/analytics-*), legacy Amplitude-JavaScript and Amplitude-Node, all MIT. Their changelogs have no table of removed members, and the Browser SDK 1 → 2 migration guide is prose, on a live page only.
Versioning
By path (/2/httpapi, /api/2/, /v1/).
Why not yet
The Developer API spec has 0 deprecations and 0 removals over all 10 commits that touched it. Its 24 changes that look breaking are refactors (a request becoming a oneOf, untyped fields becoming $refs, a schema renamed), none called breaking in the CLI's changelog.
The openapi plugin's deprecations-only rule would emit nothing, and there's no real historical change to replay.
Revisit when
The Developer API deprecates or removes an operation, or reaches 1.0. Then the openapi plugin applies with an adapter on developer-cli's tags (version = the tag's SemVer), after checking the spec's license.
Or an SDK major ships a committed migration guide with a table of removed members, which would suit the removedmembers plugin.
Activity
brandonphelps1212 commentedon Nov 19, 2026
Research findings (checked 2026-11-19): not yet, revisit at the Developer API's first deprecation or 1.0
Sources
/releases/feed.xml. It's a product changelog with a rolling 200 items. 2 items match deprecation words: one deprecates MCP tools, not an API, and one is a "No" answer.openapi/bundled/openapi.bundled.yamlin amplitude/developer-cli, tagsdeveloper-cli-v0.2.0tov0.7.0, since 2026-06. The repo is MIT, but the spec's owninfo.licensesays "Proprietary". The classic APIs (HTTP V2, Batch, Export, Dashboard REST) have no published spec.@amplitude/analytics-*), legacy Amplitude-JavaScript and Amplitude-Node, all MIT. Their changelogs have no table of removed members, and the Browser SDK 1 → 2 migration guide is prose, on a live page only./2/httpapi,/api/2/,/v1/).Why not yet
oneOf, untyped fields becoming$refs, a schema renamed), none called breaking in the CLI's changelog.openapiplugin's deprecations-only rule would emit nothing, and there's no real historical change to replay.Revisit when
openapiplugin applies with an adapter on developer-cli's tags (version = the tag's SemVer), after checking the spec's license.removedmembersplugin.Leaving this in Backlog.