What we monitor
The current public source registry covers five providers and the official release-note or lifecycle surfaces below. Coverage can expand only when a source has a stable canonical URL and a parser that can preserve the provider's facts.
How a change becomes public
The system keeps immutable source snapshots. It extracts structured facts, compares them with the previous version, and groups a meaningful delta into one canonical event. An event is eligible for public display only when it has official evidence and an approved review status.
What the public record contains
Published events expose the provider, scope, change type, dates, before-and-after field values, and links to official evidence. Stack applicability, priority, ownership, and notification state remain private to the workspace that declared the dependency.
What we do not access
ReleaseDelta does not require provider API keys, production request or response bodies, or source-code repository access. Matching starts from the providers, models, APIs, SDKs, and features that a user explicitly declares in a Stack Profile.
Corrections and limits
Provider material can be revised, withdrawn, or incomplete. We keep evidence and event versions visible, and material factual changes follow the published Corrections policy. A public event is a verified provider fact, not a substitute for checking the provider source or testing a production migration.