Nightly digest ·
OpenAI puts a date on its old voice models; the end-of-July cluster is now this week
OpenAI has deprecated its legacy audio, realtime, and transcription API models and set 20 January 2027 as the day they stop responding — a rename-not-rebuild migration for any voice or speech app that pins those model IDs. The monitored feeds were quiet, and the shutdown cluster we have been tracking is now days away, led by Bitbucket app passwords on Monday.
One real addition to the calendar tonight, from the discovery scan, plus the end-of-July cluster closing to within days. The monitored feeds were quiet — no new imminent shutdowns and no moved dates.
New to the calendar
- OpenAI deprecates its legacy audio, realtime, and transcription models (source). On 20 July 2026 OpenAI marked a whole cohort of its voice and speech models as deprecated and gave them a hard removal date of 20 January 2027. The list is the workhorse set behind a lot of current voice apps:
gpt-realtimeandgpt-realtime-mini(speech-to-speech, the models behind live voice agents),gpt-audioandgpt-audio-mini, the oldergpt-4o-audio/gpt-4o-realtimesnapshots, and thegpt-4o-mini-transcribe-2025-03-20transcription snapshot. Deprecated means they keep working through the second half of 2026; on 20 January 2027 a call that names one of them starts returning an error instead of a response. This is the failure mode that surprises teams, because nothing degrades gradually — a hardcoded model ID works for months and then throws on a single morning. The good news is OpenAI published a one-to-one replacement for each retired model (realtime →gpt-realtime-2.1, audio →gpt-audio-1.5, the transcription snapshot →gpt-4o-mini-transcribe-2025-12-15), so for most teams this is a find-and-replace across code and config plus a re-run of the voice/transcription tests, not a re-architecture. Six months is a comfortable runway; the trap is only for whoever lets the date arrive first.
Also closing this week
The end-of-July cluster we have been tracking is now days out. Everything below is already on the calendar; the items re-checked against their primary source tonight (our rule for anything inside thirty days) are marked, and every re-checked date came back unchanged:
- Bitbucket Cloud app passwords — Monday 28 July, the hard removal. App passwords have been in escalating daily brownouts since 9 June; Monday is when they are gone for good. If any git remote, CI job, or integration still authenticates with a Bitbucket app password, it stops working then — move it to an API token now. Date re-confirmed unchanged tonight against Atlassian’s brownout-schedule notice.
- Adobe Lightroom API — 31 July.
- CoScreen — 31 July, the app shuts down.
- MongoDB 8.2 — 31 July, end-of-life for the rapid release. Move to a major line (8.0, or the newer 8.3, both supported to 2029) if you did not deliberately choose the rapid track. Date re-confirmed unchanged tonight.
- RabbitMQ 4.2 — 31 July, end of community support; commercial support continues to 2030. Date re-confirmed unchanged tonight.
- Rails 7.2 — 9 August, end of security support, now inside the thirty-day window. Date re-confirmed unchanged tonight.
From the monitored feeds
Nothing imminent changed in the watched sources tonight: no new shutdowns and, notably, no moved dates in the fifty monitored feeds. On a quiet night the honest report is a short one — the calendar’s near-term cluster is unchanged, and the one new item came from looking beyond the feeds, not from them.