GitHub sets July 30 as the hard shutdown for GitHub Models

GitHub confirmed on July 1 that GitHub Models will be fully retired on July 30, 2026, and any pipeline still calling into that surface now has a fixed end date rather than an open-ended wind-down. The vendor first closed the service to new customers in June; the July 1 changelog entry converts the earlier grandfathered access into a hard shutdown date, per the changelog.

What the changelog fixes in place

Two dates now anchor the timeline. New-customer access was cut off in June. Full retirement lands on July 30, 2026. GitHub is publishing the schedule through its changelog rather than a separate deprecation page, which means the primary artifact platform teams have to reference is a dated blog post, not a versioned policy. The consequence is that the continuity language previously attached to the closure now carries an expiration.

Where this bites in a pipeline

Any workflow that pulls through GitHub Models for release-note drafting, PR summarisation, test triage or eval steps stops working the moment retirement takes effect. There is no soft rate-limit at the far end of the window; the service is gone. Rollback is not a lever here, because there is nothing to roll back to.

The migration itself is not a one-line change. Anything replacing GitHub Models, whether a hosted gateway, a direct provider account or an internal broker, comes with its own key handling, billing surface and rate-limit shape. Teams that treated the GitHub Models key as boring infrastructure will find out how many pipelines depend on it during the audit, not before it.

Roughly four weeks is not much room. What is fixed is the date. What is not fixed is anyone's inventory.