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 Elasticsearch, I want patch-it to know when Elasticsearch breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
Find Elasticsearch'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/elasticsearch.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 Elasticsearch 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
Done in #127 (merged). Per the current convention the plugin is live in docs/plugins.md; patch-it's hosted ingestion service picks it up from the next automatic release. Its events carry Elasticsearch versions (9.0.0), which the patch-it client's package gate already reads.
Activity
brandonphelps1212 commentedon Nov 19, 2026
Done in #127 (merged). Per the current convention the plugin is live in docs/plugins.md; patch-it's hosted ingestion service picks it up from the next automatic release. Its events carry Elasticsearch versions (9.0.0), which the patch-it client's package gate already reads.