What does ReleaseDelta monitor?
ReleaseDelta currently monitors official release-note and model-lifecycle sources across OpenAI, Anthropic, Google Gemini, Amazon Bedrock, and Azure OpenAI. The public Coverage page lists the current provider and change-type boundaries.
Does ReleaseDelta read API keys or production traffic?
No. You declare the providers, models, APIs, SDKs, or features that matter to your team. ReleaseDelta does not ask for provider credentials, production request or response bodies, or source-code repository access.
How is a change verified?
The system preserves an immutable source observation, extracts structured facts, and compares the new observation with the prior version. A public event must include official evidence and pass the approval gate before it is displayed.
What is the difference between a deprecation and a breaking API change?
A deprecation or lifecycle event changes the support or availability window for a model or capability. A breaking API event changes a contract, request, response, SDK behavior, or platform behavior that may require code changes. Both remain linked to their official evidence.
Can a provider change affect one team but not another?
Yes. Public facts are shared, but applicability depends on the dependencies declared in each Stack Profile, including resource type, model or API name, platform, SDK, region, environment, and priority context.
Can I report an incorrect event?
Yes. Use the Corrections policy or email support@releasedelta.com with the event URL, the disputed statement, and an official source supporting the correction. Material corrections retain their audit trail.