Swap retiring AI models before they break production.
ModelExpiry finds the model IDs in your repos, checks each one against the providers’ retirement schedules, and opens a pull request to the official replacement.
$ npx modelexpiry scanFree on 3 repos. No account for the CLI.
npx modelexpiry fix
The ID changes. Nothing else does.
Locally, the CLI previews each swap and applies it in place. On GitHub, the App opens the same change as a pull request, with a checklist for your evals.
⚠ gpt-4o-2024-08-06 shuts down on 2026-12-08 (24 days)
OpenAI recommends gpt-5.1. Source: OpenAI deprecations, fetched 2026-11-14
This PR swaps the model ID in 2 files and changes nothing else.
Before you merge
☐ Run your evals on the prompts this model serves
☐ Check structured outputs and tool calls still parse
☐ Compare latency and cost on real traffic
ModelExpiry never merges. Close this PR to snooze it until D-7.
Replace gpt-4o-2024-08-06 with gpt-5.1
GitHub App · GitHub Action
A check on every pull request, one report per repo.
The check fails only when a pull request adds a model that is on its way out. Existing debt goes to a single Issue, kept up to date.
This pull request adds gpt-4o-2024-08-06, which OpenAI shuts down on 2026-12-08.
gpt-5.1.Model retirement report #57
Open Updated by modelexpiry 2 h ago
| Model | Status | Shutdown | Fix |
|---|---|---|---|
| gpt-4o-2024-08-06 | ▲ deprecated | in 24 days | #412 |
| claude-sonnet-4-20250514 | ▲ deprecated | in 62 days | #88 |
| gemini-2.0-flash-001 | ◐ legacy | in 83 days | #19 |
| gpt-4.5-preview | ✕ retired | calls fail | #77 |
Start free. Upgrade when you outgrow 3 repos.
Prices in USD, taxes handled by Stripe.
Free
$0forever
- CLI and GitHub Action, unlimited
- GitHub App on 3 repos
- Auto-PRs, checks, report Issue
- Email alerts at D-90 to D-7
Indie
For solo builders$5/ month
- Everything in Free
- Unlimited personal repos
- Slack, Discord and signed webhooks
- Your own alert lead times
Team
$59/ month per GitHub org
- Unlimited org repos, 10 members
- See what runs in production
- Bedrock and Azure dates
- Weekly report
Questions
Do you store my code or send it to an LLM?
No. The App reads each repo in memory and discards it; we keep the path, the line and the model ID. The CLI and the Action send nothing at all.
Will you merge the pull request for me?
Never. ModelExpiry opens the pull request, your own CI runs on it, and you decide. Close it to snooze the alert until seven days before the shutdown.
Where do the retirement dates come from?
From each provider’s official deprecation pages. Every date keeps its source link and the time we fetched it. New announcements go out within hours; a change that contradicts a published date waits for a person to check it.
What if a model I use is not in the registry?
Then it is never reported: an ID we do not know is not a finding. New models are added as their providers publish them.