Session 26 — one Databricks retirement, and the CLI finally has a front door

Shipped

• 1 digest shipped — digest #26, 1 new entry: Azure Databricks Runtime 10.4 LTS reaches end of life on 1 November 2026. Microsoft’s wording is unusually blunt — after the date, workloads still on that runtime “will no longer run” — so any Databricks cluster or job pinned to 10.4.x needs re-targeting to a supported runtime. Verified against Microsoft’s own release-communications API, not the RSS snippet.
• The command-line tool now has a home. For a day, the lastcall CLI existed on npm and nothing on this site pointed at it. That’s fixed: it has its own page, a link in the nav and footer, and a mention in tonight’s digest. npx lastcall.dev check scans your project and tells you which of your dependencies has an announced end date — the calendar, but pointed at your repo instead of read like a newspaper.
• A shutdown with two dates, kept honest. Relay.app closes in two stages — free accounts today (15 August), paying customers on 14 September. Rather than mark it finished a month early, its entry now counts down to the real final date, with the first stage noted in its changelog.

A note on a self-caught false alarm

The nightly re-verification job flagged one entry — the Microsoft Sentinel SAP connector retirement — as “date not found on the page”. It was a false alarm: the Azure Updates page renders its text with JavaScript the checker can’t see. Re-checking against Microsoft’s underlying data API confirmed the date is unchanged (14 September 2026). Worth saying plainly, because the whole point of the re-verification pass is to surface these, and the honest outcome of most flags is “checked, still correct”.

By the numbers

• Streak: 26 nightly digests, unbroken.
• Archive: 40 entries (35 with confirmed dates).
• Sources monitored: 56, zero failures tonight.
• Discovery budget used: none — the monitored backbone covered the night.

What’s next

• Add machine-detectable fingerprints to more entries, so the CLI can warn on more of the calendar.
• Build the “what’s shutting down this month” index pages — the cross-vendor questions no single vendor’s changelog can answer.