OpenAI is removing the GPT-5 and o3 snapshots — gpt-5-2025-08-07, o3-2025-04-16, o3-pro-2025-06-10 — from the API on 11 December 2026; OpenSSL 3.0 reached end-of-life today

No new sunsets crossed the monitored sources or discovery searches tonight, and no corrections are outstanding. Today’s dated event on the board arrived on schedule — OpenSSL 3.0 reached end-of-life — and tonight adds one new, detectable entry from a vendor’s own deprecation schedule. Tonight’s three re-verification flags were again the Microsoft pages that render their dates in JavaScript (Sentinel SAP connector, Azure Automation Python/PowerShell runtimes, Exchange Web Services); each was re-confirmed correct by hand against Microsoft’s release-communications API and page metadata, not data errors.

New (archive): OpenAI removes the GPT-5 and o3 dated snapshots — 11 December 2026

OpenAI’s deprecations page records that on 11 June 2026 it notified developers using older GPT-5 and o3 model snapshots that they would be removed from the API on 11 December 2026. Six dated snapshots are listed, each with a gpt-5.6 replacement:

• gpt-5-2025-08-07 → gpt-5.6-sol
• gpt-5-mini-2025-08-07 → gpt-5.6-terra
• gpt-5-nano-2025-08-07 → gpt-5.6-luna
• gpt-5-pro-2025-10-06 → gpt-5.6-sol (reasoning.mode: pro)
• o3-2025-04-16 → gpt-5.6-sol
• o3-pro-2025-06-10 → gpt-5.6-sol (reasoning.mode: pro)

The distinction that matters is alias versus snapshot. If your code calls the bare gpt-5 or o3 model name, OpenAI keeps repointing it to a current model and this date does not touch you. The exposure is the opposite habit — pinning the exact dated snapshot for reproducibility, which teams do inside eval harnesses, regression baselines, batch pipelines and config files that nobody has opened in months. Those calls return an error after 11 December. Because swapping the underlying model can shift output shape, latency and cost, the safe move is to re-point and re-run evals against the gpt-5.6 replacement before the date, not on it.

This entry is detectable: the lastcall CLI fingerprints the six exact snapshot ids — OpenAI-exclusive names called against OpenAI’s own API, so a match is a true signal — while deliberately leaving the surviving gpt-5/o3 aliases and the gpt-5.6 replacements alone. It sits alongside the existing 23 October 2026 GPT-4/GPT-3.5/o1/o3-mini removal as one wave of the same rolling schedule.

On the board

• 7 September — today: OpenSSL 3.0 reached end-of-life. After today the 3.0 LTS branch receives no further upstream fixes, security included; if you consume it through a distribution (RHEL, Ubuntu LTS), your vendor’s own backport window may extend past this date — check before assuming you are exposed, and check before assuming you are safe.
• 10 September: the GitHub Copilot MAI-Code-1-Flash deprecation.
• 14 September: the Relay app and Microsoft Sentinel SAP connector agent retirements.

Further out: the Azure Maps Render v1 API retirement (17 September), OpenAI’s Sora 2 video API shutdown (24 September), a cluster on 30 September and 1 October, the GitHub Copilot model deprecations (2 October), OpenAI’s 23 October API removals, then .NET 8 and 9 end of support (10 November) and PostgreSQL 14 end-of-life (12 November). The full board with live countdowns is on the calendar.