Skip to content

I6.2 · Watch Anthropic #36

Open
Open

Description

@adssib

Part of #9

See also I21, more sources for the providers we watch. Updated 2026-11-20 to the provider / source model (I19).

Story

As a developer who calls Anthropic, I want patch-it to know when Anthropic breaks, deprecates or retires something in its API or SDKs, so I get the fix before production does.

Live today: model retirements and the Python SDK's 1.0 migration guide. This story covers the rest.

Missing sources

Proposed; check each before writing it (verify, don't guess; leave TBD if unknown). Ids follow the provider/source form (I19.2).

  • anthropic/api · kind openapi · layer api · the OpenAPI spec the official SDKs are generated from, if public (each SDK repo's .stats.yml names it): operations and parameters removed or deprecated between spec versions
  • anthropic/python · kind changelog · layer sdk · anthropics/anthropic-sdk-python CHANGELOG.md at each tag: breaking changes in every release, not only 1.0
  • anthropic/typescript · kind changelog · layer sdk · anthropics/anthropic-sdk-typescript CHANGELOG.md at each tag: the same for TypeScript
  • anthropic/python-surface · kind apisurface (kind not built yet: waits for I19.10) · layer sdk · anthropic on PyPI: removed or renamed methods and parameters between releases

Subtasks

  • For each source: link, date checked, why it's the best source and a short quote, in providers/anthropic.md under Why this source
  • One source per PR, registered under the Anthropic provider
  • Saved copies in testdata/ (row in testdata/README.md: URL, date fetched, license, quote), a golden file, and one drop test
  • The source lists its versions (I19.8) where its kind supports it
  • Note what the client needs to fix it (an existing file-type handler, or a new one)
  • make check passes

Acceptance criteria

  • Each new source emits events with source_url and an exact source_excerpt
  • The drop test produces no event
  • The provider page lists every source with its date checked

Activity

  1. adssib commented on Nov 21, 2026

    @adssib
    ContributorAuthor

    Changelog candidates for this provider's SDKs were checked for #232 and skipped: across every release section at HEAD (2026-11-20) the release-please / Stainless changelogs never name a removed symbol in a plain sentence ("This minor release includes a breaking change to …", "add support for new API version …"), so the changelog reader would emit nothing (precision over recall). The apisurface sources in this story are the better fit for these SDKs.

    🤖 Generated with Claude Code

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions