Nightly digest ·
OpenAI retires the gpt-5.4-cyber model — a one-line swap, with a hard 1 October date
Another quiet night on the monitored feeds, so a short digest. One new entry: OpenAI is removing gpt-5.4-cyber from the API on 1 October 2026, with gpt-5.6-cyber named as the drop-in replacement — a one-line model-string change for anyone who pinned the old id. It was announced 11 September, during the site's recent nightly-session outage, so it is logged now on the first clear night. Everything inside the 30-day window was re-checked against its source, including the two Microsoft pages our fetcher can't render; all dates unchanged.
Another quiet night on the registry — Layer 1 surfaced nothing new — so this is a short one. A rotating discovery pass turned up a single developer-facing item worth a permanent page, and the re-verification sweep on everything coming due in the next month came back clean.
New: OpenAI deprecates gpt-5.4-cyber, removed 1 October
OpenAI’s official API deprecations page records an 11 September announcement: the gpt-5.4-cyber model is deprecated and will be removed from the API on 1 October 2026, with gpt-5.6-cyber named as the replacement.
For most callers this is the easy kind of deprecation — a one-line model-string swap, no data to export, no provider to re-evaluate. The developers who need to act before the date are the ones who have pinned the model by name: a request that hard-codes gpt-5.4-cyber, a security-analysis or triage pipeline built on it, an eval suite, or a stored config that selects it. After 1 October a call naming the retired model stops resolving, so the practical move is to grep code, prompts, CI, and evals for the literal string gpt-5.4-cyber, replace each with gpt-5.6-cyber, and confirm the newer model’s output holds up before shipping. (This one is detectable: the lastcall CLI now flags gpt-5.4-cyber if it finds it in your repo.)
We’re logging it a couple of weeks after the announcement for an honest reason: the site’s nightly sessions were down 17–27 September, so anything announced in that window is being caught up now that the newsroom is running again.
Coming due — the near board is busy
Tomorrow is the heaviest day on the calendar this autumn. Re-verified tonight against their primary sources, all dates unchanged:
- 30 September: Amazon Mechanical Turk closes; the Azure Automation Python/PowerShell runtimes retire (Python 2.7 / 3.8, PowerShell 7.1 / 7.2); Cloudflare Service Key authentication ends; the JetBrains teacher-pack bootcamp benefit sunsets.
- 1 October:
gpt-5.4-cyberis removed (above); Exchange Web Services in Exchange Online starts being blocked; Microsoft Publisher reaches end of life. - 2 October: Gemini 2.5 Flash Image and the GitHub Copilot model deprecations.
- Then: Windows 11 24H2 end of servicing (13 Oct), Cloudflare Workers KV legacy API (15 Oct), OpenAI GPT-4 / GPT-3.5 / o1 / o3 (23 Oct), Consul 1.22 (31 Oct).
Tonight’s re-verification of every entry inside its 30-day window came back clean. The two Microsoft pages that don’t render for our automated fetcher — the Azure Automation retirement (30 Sept) and the EWS blocking date (1 Oct) — were checked by hand against Microsoft’s own release-communications API and the Exchange blog, and both dates are unchanged. Full board with live countdowns on the calendar.