Normalize the official event
Capture provider, seller, product surface, exact model or feature, source URL, publication date, observed date, effective date, region, access state and prior value. Preserve the source wording for announced, preview, restricted, generally available, deprecated and retired states. A dated claim is not the same as a purchased route.
Map the affected route and workflow
Join each event to the approved inventory by account, endpoint, model alias, tool and destination. Record data classes, users, reviewers and the current baseline. If no approved workflow is affected, close the event as monitored with the reason. Do not create one new article for every release when a durable canonical already owns the decision.
Choose the smallest required action
| Action | When it fits | Owner evidence |
|---|---|---|
| Source recheck | The event may be stale or route-specific | New checked date and source snapshot |
| Contract review | Terms, retention or support changed | Executed agreement and delta |
| Regression | Output, permissions, tools or safeguards may change | Frozen set, failures and reviewer |
| No action | No approved route is affected | Reason and next freshness check |
Keep regression and rollback attached
When a candidate affects substantive output, permissions, tool calls, latency, completed-task cost or safeguards, run the frozen representative set before promotion. Preserve blocking failures and reviewer corrections rather than an average alone. Keep the prior route available until the observation window passes.
Operate a correction and freshness policy
Show the last successful source check, stale threshold, missed-run status and next review. Archive the prior value or structured delta. A release is not a migration instruction; it is an event whose impact remains Unknown until the assigned owner accepts the action.
FAQ
Should every model release create a page?
No. Create or update a URL only when a durable distinct reader decision survives canonical review.
Does a deprecation notice require immediate migration?
It requires an impact check and plan before retirement. The replacement still needs route verification and regression.
How fresh is a static tracker?
Publish an explicit checked date, freshness SLA and failed-source state. Never imply continuous monitoring from a static page.
Sources checked
- OpenAI API changelog, checked 2026-09-03.
- Gemini API release notes, checked 2026-09-03.
- Gemini model deprecations, checked 2026-09-03.
- Claude model deprecations, checked 2026-09-03.
- AI Risk Management Framework, checked 2026-09-03.
Operational information, not legal advice. Verify current terms, account configuration and applicable professional duties before use.