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 Algolia, I want patch-it to know when Algolia breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
Find Algolia'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/algolia.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 Algolia 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 #113 (merged): algolia-search, algolia-ingestion and algolia-recommend. They run in the hosted ingestion service once they're in a tagged release, and their rows in docs/plugins.md move from paused to live then. Like cloudflare and supabase, their events are date-versioned, so the patch-it client needs its rule for date-versioned api_operation events first.
Activity
brandonphelps1212 commentedon Nov 19, 2026
Done in #113 (merged): algolia-search, algolia-ingestion and algolia-recommend. They run in the hosted ingestion service once they're in a tagged release, and their rows in docs/plugins.md move from paused to live then. Like cloudflare and supabase, their events are date-versioned, so the patch-it client needs its rule for date-versioned api_operation events first.