GitHub Models is not merely being deprecated at some vague point in the future. It is shutting down on 30 July 2026. If a prototype, workflow, or internal tool still calls its inference API, the useful response is to find that dependency now rather than discover it through a production error at the end of the month.
GitHub’s retirement notice says the playground, model catalogue, inference API, and bring-your-own-key endpoints will all go away. There are also planned brownouts on 16 and 23 July, when requests will temporarily fail. GitHub points general model-access workloads towards Microsoft Foundry and GitHub-native development workflows towards Copilot.
The brownouts are a useful forced test if you treat them that way. Search repositories and deployment configuration for the endpoint and credentials, identify the owner of each caller, then make sure failure is visible rather than silently swallowed. A replacement is not complete just because the first request works; model names, limits, authentication, response shapes, cost controls, and data-handling rules all need checking.
This is also a reminder not to build around a convenient preview as if it were permanent infrastructure. Previews are great for proving an idea. Once the idea matters, the provider boundary needs to be explicit enough that a shutdown is a migration, not a rewrite.