Skip to content

Warn from server deprecation headers - #54

Open
yudelevi wants to merge 3 commits into
developmentfrom
feat/deprecation-headers
Open

yudelevi wants to merge 3 commits into
developmentfrom
feat/deprecation-headers

Conversation

@yudelevi

@yudelevi yudelevi commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Old SDKs learn about a retired endpoint only from a new release. Reading the Deprecation header lets any endpoint announce itself, so warnings stop being hardcoded in email.py. Warns once per method and path template per process.

Hardcoded warnings needed an SDK release for every deprecation and
fired on each call, even without a request. The server now sends
Deprecation on retired routes, so the transport warns once per
endpoint and new deprecations reach existing SDK versions.
@greptile-apps

greptile-apps Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Automatic reviews are disabled for this repository. Configure in Code Review Settings.

The API dropped steps and tightened validation, so the stepwise client would be rejected with 422 before it ever shipped.
contacts.count stays supported, so it no longer warns. Deprecation
warnings now come from the server's headers on every call and are
visible by default, so callers cannot miss a sunset.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant