[bogdanr]

What

Follow-up to #3952. That PR removed models that were already shut down. This one removes 47 entries that were still being served but had been formally deprecated with a retirement date by the platform that runs them.

Pure deletions in provider.json and vertex.json (0 added lines; the remaining entries' formatting is untouched). No code changes.

Updated 2026-10-22: rebased onto current main and added the GPT-4 series snapshots that OpenAI deprecated on 2026-10-14 (retiring 2027-01-14). Several retirement dates listed below have now passed, so those entries are already dead rather than "about to break".

Scope rule

A model is removed only if its platform operator has marked it deprecated and announced a retirement date. Each provider list is checked against its own platform, since Anthropic notes that Bedrock and Google Cloud set their own schedules.

Not removed: models labelled only Legacy (no retirement date), models with a replacement listed but no shutdown date, and aliases whose dated snapshot is deprecated but the alias itself isn't.

Removed

Provider	Removed	Retirement	Source
openai (15)	o1, o1-2024-12-17, o3-mini, o3-mini-2025-01-31, o4-mini, o4-mini-2025-04-16, gpt-4.1-nano, gpt-4.1-nano-2025-04-14, gpt-4o-2024-05-13, gpt-4-turbo, gpt-4-turbo-2024-04-09, gpt-4, gpt-4-0613, gpt-3.5-turbo, gpt-3.5-turbo-0125	2026-10-23	OpenAI deprecations, "2026-04-22: Legacy GPT model snapshots"
openai (4)	gpt-5-2025-08-07, gpt-5-mini-2025-08-07, gpt-5-nano-2025-08-07, o3-2025-04-16	2026-12-11	Same page, "2026-06-11: GPT-5 and o3 model deprecations"
openai (3)	gpt-5.1, gpt-5.3-codex, gpt-5.4-nano	2027-04-01	Same page, "2026-10-01: GPT-5.3-Codex, GPT-5.1, GPT-5.4-Nano"
openai (5)	gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14, gpt-4.1-mini-2025-04-14	2027-01-14	Same page, "2026-10-14: GPT-4 series model deprecations"
claude_code (1)	claude-sonnet-4-5-20250929	2026-11-30	Anthropic model deprecations, announced 2026-09-30
bedrock (11)	Claude Sonnet 4 (anthropic., us., eu., global.), Opus 4.1 (anthropic., us.), Sonnet 4.5 (anthropic., us., eu., global.), Haiku 3.5 (anthropic.)	Sonnet 4: 2026-10-14 (passed); Opus 4.1: 2027-01-08	AWS model lifecycle (legacy) for the dates; all four are marked deprecated in Anthropic's Bedrock model table
vertex_ai_anthropic (4)	claude-opus-4-1@20250805, claude-opus-4@20250514, claude-sonnet-4@20250514, claude-sonnet-4-5@20250929	Not published by Google	All marked deprecated in Anthropic's Google Cloud model table
vertex_ai (2), vertex.json (2)	gemini-2.5-pro, gemini-2.5-flash	2026-10-20 (passed)	Vertex model versions and lifecycle

Calls reviewers may want to check

1. Claude on Bedrock/Vertex without a partner date. AWS gives dates for Sonnet 4 and Opus 4.1 but doesn't list Sonnet 4.5 or Haiku 3.5 yet, and Google publishes no dates for Claude 4.x. I removed them because Anthropic's own tables for those platforms label them deprecated. Happy to restore any of them if you'd rather wait for the partner's date.
2. Gemini 2.5 differs by platform. Vertex retires gemini-2.5-pro/gemini-2.5-flash on 2026-10-20, but the Gemini API explicitly says 2.5 is not deprecated. So they're removed from vertex_ai/vertex.json only and kept in google_ai_studio.
3. OpenAI aliases kept. gpt-5, gpt-5-mini, gpt-5-nano, o3, gpt-4o, gpt-4o-mini, gpt-4.1 and gpt-4.1-mini stay: only their dated snapshots are deprecated, not the aliases.

Deliberately kept

• Resellers and non-API backends (codex, vivgrid, opencode_zen, opencode_go, etc.): they set their own availability. For example, codex still lists gpt-5.3-codex. Same approach as chore: remove retired models from static provider catalogs #3952.
• MiniMax M2.5/M2.1/M2: listed under "Legacy Models" with no retirement date.
• Gemini API gemini-3-flash-preview: has a recommended replacement but "No shutdown date announced".
• Z.ai and other providers: no deprecation notices found for listed models.

Not changed

• Test fixtures and benchmarks still use IDs like claude-sonnet-4-5-20250929, gpt-4 and gpt-3.5-turbo. They're arbitrary strings that don't depend on the catalog, so changing them would just be churn.
• Out of scope, but spotted: Moonshot lists kimi-k2.5 and kimi-k2-thinking (in moonshot, and kimi-k2.5 in a few other lists), but the Kimi model list says they were already discontinued (2026-08-31 and 2026-05-25). That's chore: remove retired models from static provider catalogs #3952's category (already retired), so I left it for a separate cleanup.

Testing

• Every edit is a pure deletion (0 added lines); each was checked semantically against the original JSON with exactly those models filtered out
• cargo test -p forge_repo -p forge_app -p forge_services: 1272 passed, 0 failed

Co-Authored-By: ForgeCode noreply@forgecode.dev

[github-actions]

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

[bogdanr]

A quick status update since the stale bot flagged this one.

CI is green on all checks, and the branch still merges cleanly into main. The only new upstream commits are dependency bumps, none of which touch provider.json or vertex.json.

Several models this PR removes are retired in the next two weeks:

• 2026-10-14: Claude Sonnet 4 on Bedrock
• 2026-10-20: gemini-2.5-pro / gemini-2.5-flash on Vertex
• 2026-10-23: 15 OpenAI models (o1, o3-mini, o4-mini, gpt-4, gpt-4-turbo, gpt-3.5-turbo, gpt-4.1-nano, gpt-4o-2024-05-13 and their snapshots)

Thanks!

[github-actions]

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

[bogdanr]

Updated this one so it's current and worth reviewing:

• Rebased onto main (was 59 commits behind, all dependency bumps).
• Added the GPT-4 series snapshots OpenAI deprecated on 2026-10-14, retiring 2027-01-14: gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14, gpt-4.1-mini-2025-04-14. The undated aliases are kept, since only the snapshots are named in the notice.
• Refreshed the description to note that several retirement dates have now passed, so those entries are already dead rather than "about to break".

Still pure deletions in provider.json and vertex.json (0 added lines), no code changes. cargo test -p forge_repo -p forge_app -p forge_services: 1272 passed, 0 failed.

@amitksingh1490 you approved and auto-merged #3952, which was the same kind of catalog cleanup — would you be able to take a look here? The most debatable part is Claude on Bedrock/Vertex where the partner hasn't published its own date yet (see "Calls reviewers may want to check"); happy to drop those entries if you'd rather wait for the partner schedules.

Co-Authored-By: ForgeCode noreply@forgecode.dev

[github-actions]

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

[bogdanr]

Status update: merged the latest upstream/main into the branch to clear the BEHIND state (was 20 commits behind). None of those upstream commits touched provider.json or vertex.json, so the merge was conflict-free and the diff is unchanged: 2 files, 455 deletions.

CI is re-running on the updated head. Still ready for review.

Co-Authored-By: ForgeCode noreply@forgecode.dev

[bogdanr]

Updated the OpenAI catalog with the documented latest GPT-6.1 model IDs: gpt-6.1-sol and gpt-6.1-terra. Each model ID is its documented default alias; OpenAI does not publish a separate generic gpt-6.1 alias, so none was added.\n\nValidated JSON and ran cargo test -p forge_repo provider_repo --lib (34 passed).\n\nCo-Authored-By: ForgeCode noreply@forgecode.dev