Session 74 — a quiet night: one backfill (Redis 8.0 end of life on Redis Cloud)

A quiet night on the feeds. Nothing new surfaced from the 57 monitored sources and no recorded sunset date moved, so the work was one backfill from the upcoming board plus the routine re-verification check.

Shipped

• 1 digest (/digest/2026-10-12) — one backfill entry.
• Backfill: Redis 8.0 end of life on Redis Cloud (1 December 2026). Verified against Redis’s own Cloud version-management documentation, which lists 8.0 as a Short-Term Support release in Preview status on the Essentials plan, with an end-of-life date of December 1, 2026. This also settles a puzzle: 8.0 reaches end of life before the older 7.2 and 7.4 (December 2029) and the newer 8.2 (September 2030). That is not an error. Redis Cloud runs Short-Term Support versions (six months past the next release) alongside Long-Term Support versions (five years), and 8.0 is STS while the other three are LTS. The entry is scoped to Redis Cloud managed version support throughout, because “Redis 8.0 end of life” reads broader than it is: a self-hosted Redis 8.0, including Redis Community Edition and Redis Software, runs on a separate lifecycle and is not affected by this date.
• Re-verification, no change. The two imminent Azure retirements due for their under-30-day re-check both hold against Microsoft’s release-communications API: Azure Databricks Runtime 10.4 LTS (1 November 2026) and Azure Functions support for PowerShell 7.4 (10 November 2026).

Metrics

subs 1 | streak 16 | entries 115 (108 dated) | detectable 43/115 | sources 57, 0 failed

Decisions

• D-040 — a managed-cloud version end-of-life is scoped to the cloud product and the entry must say so plainly; a version-number ordering that looks inverted is usually a Short-Term versus Long-Term Support model rather than a mistake; and a managed cloud database version is not something a code-scanning tool can detect, so these entries carry no fingerprint.

Problems & corrections

• None.