Another quiet night — but the OpenAI Assistants API is now four days from removal: what to check before 26 August

No new sunsets were confirmed to the calendar tonight — 56 monitored sources fetched clean and the discovery scan surfaced only noise. So this is a short one, pointed at what is actually close: the OpenAI Assistants API is removed on 26 August, four days out, with the Responses API as the migration path. All eleven sub-30-day entries were re-checked against their primary sources tonight and all hold, including the Microsoft Sentinel SAP connector retirement (14 September), re-confirmed against Microsoft's release-communications API. The circulating InstantDB / Instant Cloud shutdown report still has no official source, so it stays on the watch list, not the board.

Quiet feeds tonight — 56 monitored sources fetched clean, no new entries and no date changes. A padded digest would be a worse read than a short honest one, so here is the short honest one, aimed at the deadline that is actually close.

Four days out: the OpenAI Assistants API is removed on 26 August

The one imminent item worth pulling forward: the OpenAI Assistants API reaches end of life on 26 August 2026. OpenAI is removing it in favor of the Responses API, which folds assistants, threads, and runs into a single stateful primitive. If you still have code calling /v1/assistants, /v1/threads, or /v1/runs, that is the code to migrate this week.

What to check before Wednesday:

Search your codebase for assistants, threads, and runs endpoint calls, and for the OpenAI().beta.assistants / .beta.threads client paths.
Map each to its Responses API equivalent — tool calls and file search carry over, but state handling changes (you pass previous_response_id instead of managing a thread object).
The official migration guide is linked from the entry, sourced to OpenAI’s own deprecation notice.

Right behind it: Convictional (B2B trade platform, access ends 27 August), the OCI DevOps Oracle Linux 7 build runners (28 August), and a four-way 31 August cluster — GitHub Spark, Flowise, the New Relic drop-filter-rules API, and the Power Automate mobile app.

Still counting down

Further out: OpenSSL 3.0 end of life (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), the Relay paid shutdown and the Microsoft Sentinel SAP connector agent retirement (both 14 September — the Sentinel date, which our monitor cannot read off Microsoft’s JavaScript-rendered updates page, was re-confirmed tonight against Microsoft’s release-communications API), the OpenAI Sora 2 video API preview shutdown (24 September), the Azure Automation Python/PowerShell runtime cut-off (30 September), the Exchange Web Services in Exchange Online block (1 October), the Cloudflare Workers KV legacy API (15 October), the Azure Databricks Runtime 10.4 LTS end of life (1 November), and the Azure Blueprints retirement (31 January 2027). The full board, with countdowns, is on the calendar.

Watch, not board: InstantDB

No change since last night: the circulating report that InstantDB is winding down its hosted Instant Cloud service (cloud apps said to close 31 August 2027) still traces back only to a user’s forwarded email quoted on Hacker News. There is still nothing on instantdb.com, its docs, or its status page, and the GitHub repository shows no sunset notice. No official source, no entry — it stays on the watch list until Instant says something publicly, at which point we will add it with the dates verified against that source.

Want these deadlines in your repo instead of your inbox? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, reading the same public dataset this site is built on.