Azure App Service will drop Node 22 LTS support in April 2027 — and the late-August cluster starts firing tomorrow with the OpenAI Assistants API removal

A genuinely quiet feed tonight — one new entry, and it is one for the calendar’s long end, not for this week’s fire drill. The fire drill is the existing board: the late-August cluster starts firing tomorrow.

New: Azure App Service drops Node 22 LTS support on 30 April 2027

Microsoft is retiring the Node.js 22 LTS runtime stack on Azure App Service on 30 April 2027. In an official Azure Updates notice, Microsoft says that after that date “support for Node 22 LTS will end. Your apps that are hosted on App Service will continue to run, but security updates will no longer be available, and we’ll no longer provide customer service for Node 22 LTS.”

The distinction is the whole story: this is the App Service runtime stack reaching end of support, not your app being switched off. A Node-22 app keeps serving traffic after the cutoff, but the platform stops patching the runtime beneath it, so you inherit every Node 22 CVE disclosed afterward and lose Microsoft support for Node-22-specific issues. App Service is retiring the stack in step with upstream — Node 22’s own community end-of-life is scheduled for April 2027 — and points you to Node 24 LTS as the upgrade. It is a runtime version bump with a long runway; the value of logging it now is so it lands as routine maintenance rather than an April-2027 scramble.

The late-August cluster starts firing tomorrow

The stretch flagged over the last week is now at the front of the countdown:

• 26 August (tomorrow) — the OpenAI Assistants API is removed. Move /v1/assistants, /v1/threads, and /v1/runs calls to the Responses API before it goes.
• 27 August — Convictional shuts down; export catalog and order data before access ends.
• 28 August — OCI DevOps retires its Oracle Linux 7 build runners; pinned pipelines break rather than warn.
• 31 August — a four-way pile-up: GitHub Spark, Flowise cloud, the New Relic drop-filter-rules API, and the Power Automate mobile app.

Further out sit OpenSSL 3.0 (7 September), the GitHub Copilot MAI-Code-1-Flash deprecation (10 September), and the Relay and Microsoft Sentinel SAP connector agent retirements (both 14 September). And last night’s entry is still ticking: Minimus’s reg.mini.dev is now one day into its 60-day maintenance window before the registry goes dark on 22 October.

All twelve entries within 30 days were re-checked against their primary sources tonight and every one holds — including the Sentinel SAP date, which our monitor cannot read off Microsoft’s JavaScript-rendered updates page and which was re-confirmed against Microsoft’s release-communications API. The full board with live countdowns is on the calendar.

Still watching, not on the board: InstantDB

No change: the circulating InstantDB / Instant Cloud wind-down report still traces only to a forwarded email quoted on Hacker News, with nothing on instantdb.com, its docs, status page, or repo. No official source, no entry — it stays on the watch list until Instant says something publicly.

Want these dates checked against your own repo instead of read off a list? The lastcall CLI — npx lastcall.dev check — scans a project and tells you which of your dependencies has an announced end date, from the same public dataset this site is built on.