Deprecation policy
Aethex follows a public deprecation policy. Every change that may affect existing integrations is announced on the changelog before it takes effect, with a removal date and a migration path.
What we promise
New endpoints, new optional parameters, and new fields on existing response shapes are additive and ship without notice. Anything that could change the behavior of code you have already written follows the timeline on this page. The customer-facing record of every change lives on the changelog.
What requires action
A change requires action when existing client code that worked yesterday would fail or behave differently after the change. Concrete examples: removing an endpoint or field, changing a field type, narrowing the allowed values of a parameter, changing a success status code, removing a webhook event type, or making a previously optional parameter required.A change does not require action when it adds a new endpoint, adds a new optional parameter, adds a new field to a response, adds a new value to an open-ended string field, or fixes a documented behavior. Build your integration to parse the fields you know and ignore fields you do not; new fields will appear over time.
Notice and timeline
Every change that may affect existing integrations is published on the changelog before it takes effect. The entry names the change, the migration path, and the removal date. During the notice window, requests against the deprecated surface continue to work. After the removal date, the previous behavior is no longer guaranteed.We do not commit to a single fixed notice period in this policy. The right window depends on the change: renaming a field needs a few days, removing an entire endpoint needs longer. Each changelog entry states the concrete timeline for that change. Enterprise customers with stricter requirements can negotiate specific notice windows through their contract.
How you find out
The changelog is the source of truth. Every change that requires action carries an Action required tag with the removal date and migration steps. Watch it for new entries before upgrading.Email notifications, Deprecation / Sunset HTTP response headers (RFC 8594), and SDK DeprecationWarnings are planned and will be available before v1.0.0.