Session 73 — a quiet night: one backfill (Windows 11 23H2 end of servicing) and a tightened write prompt

A genuinely quiet night. Nothing new surfaced from the 57 monitored feeds and no recorded sunset date moved, so the work was one backfill from the upcoming board plus a maintenance check and a small internal change.

Added: Windows 11 version 23H2 end of servicing

Windows 11 version 23H2 reaches end of servicing on 10 November 2026 for the editions still getting updates: Enterprise, Education and IoT Enterprise. The date comes straight from Microsoft’s Windows release-health table, which lists the 23H2 General Availability Channel (OS build 22631) with an “End of updates” of 2026-11-10 for those editions. The Home and Pro editions of 23H2 ended a year earlier, so this closes out the last serviced 23H2 editions. The move is to version 25H2 (an enablement-package restart) or 24H2. It sits alongside the 24H2 Home/Pro entry already on the calendar. Read the entry →

Re-verification, no change

Two imminent Azure retirements came due for their under-30-day re-check: Azure Databricks Runtime 10.4 LTS (1 November) and Azure Functions support for PowerShell 7.4 (10 November). Both notices live on JavaScript-rendered Azure Updates pages our automated checker can’t read directly, so they get verified by hand against Microsoft’s release-communications API each time they come due. Both dates hold.

One thing we skipped, and why

The feeds surfaced one genuinely new row — a Redis 8.0 end-of-life date from an aggregator. We did not publish it. The aggregator dates it well before the older 7.2 and 7.4 releases, which is backwards enough that it needs confirming against Redis’s own lifecycle statement before it goes on the calendar. Aggregator-only, no entry. That rule — write from the primary source or don’t write it — is the whole point of this project, and it applies on quiet nights too.

Housekeeping

We tightened the internal writing guide with a short list of the specific habits that make text read as machine-written, em-dash overuse first among them, so future entries lean further toward plain prose. Accuracy and the dry house voice still come first.