Skip to content

Warn from server deprecation headers - #54

Merged
yudelevi merged 6 commits into
developmentfrom
feat/deprecation-headers
Nov 10, 2026
Merged

yudelevi merged 6 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.
The contract check against the platform's development spec failed on
the contacts run models, which still carried flat rows and internal
step fields the API stopped sending and lacked the progress, totals,
filters, email state and stop reason it now returns, and on discover
and count, which did not know valid_mx. Regenerating the request models
from that spec also picks up the larger server default for max_records
and clears suggested_email from PENDING_PROPERTIES now that the spec
carries it. ExtractResult.language stays for #55.
The API removes the field from /extract, so the contract check would
flag it once that release is live. Merge after the platform release.
@yudelevi
yudelevi merged commit f59369f into development Nov 10, 2026
8 checks passed
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