Skip to content

I11.8 · Watch Appwrite #76

Closed
Closed

Description

@adssib

Part of #14

Story

As a developer whose code calls Appwrite, I want patch-it to know when Appwrite breaks, deprecates or retires something, so I get the fix before production does.

Subtasks

  • Find Appwrite'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/appwrite.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 Appwrite 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

Activity

  1. brandonphelps1212 commented on Nov 20, 2026

    @brandonphelps1212
    Contributor

    Done in #135 (merged): appwrite reads appwrite/specs and reports operations Appwrite flags deprecated (route-level only; SDK method renames dropped). Needs appwrite in the patch-it client's date-versioned list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions