GitHub announces the deprecation of selected Copilot models, changing the supported model choices for coding workflows that depend on them.
state: expiredheat: lowuncertainty: mediumknownscott: lowgithub-copilot model-lifecycle coding-agentsGitHub
What is this?
GitHub is retiring selected models offered through Copilot and asking users to update workflows and integrations to supported alternatives; Enterprise administrators may also need to enable alternatives through model policies. An official January 13, 2026 changelog snippet announces a February 17 retirement across Copilot experiences, while an official roadmap snippet describes six model retirements on August 31, 2026. Secondary sources instead give September 1 for the latter wave, so the supplied results cover multiple announcements and do not establish which wave the case refers to or its exact affected models and replacements.
Why it matters to Scott
This is another instance of Scott’s existing Model Perishability position: model dependencies require swapping, re-evaluation and exit planning, rather than a newly established adoption of that position by GitHub. His GitHub account page records Copilot adoption, but the unidentified retirement wave and affected models leave no demonstrated impact on his current workflows; the radar tracks Copilot, not this specific retirement in the supplied hits.
ip:concept.model-perishabilitywork:project.githubradar:concept.github-copilot
queries asked of Scott's wikis
- Copilot dependencies coding workflows model policies
- Model retirement vendor dependency migration strategy
- Coding agent harness model portability provider abstraction
- Model upgrades regression evaluations coding agents
- Pinned model versions reproducible AI workflows
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-09T19:40:48Z
The case has reached its review horizon without evidence identifying the retirement wave, affected models, or migration terms. The deprecation notice remains credible, but with no confirming update expected, this underspecified episode no longer earns active tracking; a concrete workflow impact would warrant reopening.
2026-09-07T19:39:04Z
No new evidence clarifies which Copilot retirement wave this announcement concerns or whether it affects Scott’s workflows. The linked story and reconstructed changelog echo remain one evidentiary line: credible notice of a lifecycle change, but insufficient scope to establish a migration decision.
2026-09-07T19:32:56Z
grounded: known/low — This is another instance of Scott’s existing Model Perishability position: model dependencies require swapping, re-evaluation and exit planning, rather than a n
2026-09-07T19:28:26Z
case created — This first-party model-lifecycle change is distinct from the existing Copilot review-billing episode.
Decision trace
- 09-10 05:40expireThe case has reached its review horizon without evidence identifying the retirement wave, affected models, or migration terms. The deprecation notice remains credible, but with no confirming update ex
- 09-10 05:40alert_silentThere is no new consequential delta to alert on. The reconstructed announcement still lacks the scope needed to establish an actionable change for Scott; this is not a reason to doubt that a deprecati
- 09-10 05:40alert_routeThere is no new consequential delta to alert on. The reconstructed announcement still lacks the scope needed to establish an actionable change for Scott; this is not a reason to doubt that a deprecati
- 09-08 05:39repriceNo new evidence clarifies which Copilot retirement wave this announcement concerns or whether it affects Scott’s workflows. The linked story and reconstructed changelog echo remain one evidentiary lin
- 09-08 05:39alert_silentThe announcement remains credible, but no affected models, applicable deadline, or migration terms have been newly established. This can wait for the next briefing; the gap is actionable scope, not in
- 09-08 05:39alert_routeThe announcement remains credible, but no affected models, applicable deadline, or migration terms have been newly established. This can wait for the next briefing; the gap is actionable scope, not in
- 09-08 05:36alert_silentThe linked GitHub changelog establishes a deprecation announcement, but the supplied evidence names neither the affected models nor retirement dates or migration terms. Without those details, it estab
- 09-08 05:36surface_candidateThe linked GitHub changelog establishes a deprecation announcement, but the supplied evidence names neither the affected models nor retirement dates or migration terms. Without those details, it estab
- 09-08 05:36alert_routeThe linked GitHub changelog establishes a deprecation announcement, but the supplied evidence names neither the affected models nor retirement dates or migration terms. Without those details, it estab
- 09-08 05:32groundThis is another instance of Scott’s existing Model Perishability position: model dependencies require swapping, re-evaluation and exit planning, rather than a newly established adoption of that positi
- 09-08 05:28createThis first-party model-lifecycle change is distinct from the existing Copilot review-billing episode.