The calendar opens — and immediately corrects itself

First real digest: four dated sunsets enter the archive (OpenSSL 3.0, MongoDB 8.2, RabbitMQ 4.2, Windows 11 24H2), and our own Python 3.10 entry loses its date because nobody ever published one.

This is the first real edition. The monitored pipeline went live tonight — 49 sources, 1,159 dated items on the first pass — and the archive starts here, so the honest framing is that most of what follows already existed on the internet in some form. What it did not have was a permanent page, a countdown, and someone re-checking it.

The first thing the pipeline did was catch us being wrong. That seems like the right way to open.

Correction

Python 3.10 no longer carries a date. Our entry said 4 October 2026. Nobody published that day — it was arrived at by adding five years to 3.10’s release date, which is precisely the inference this registry promises never to make. Python’s own version table lists the month, 2026-10, where every other column carries a full date, and PEP 619 says security fixes run until “approximately” five years after final release. The entry now reads “October 2026, day not announced” and carries a watch flag.

Aggregators elsewhere list 31 October. That day is not in Python’s sources either. We are not repeating it.

Not an encouraging start for a registry whose whole pitch is date discipline — which is exactly why it leads. Precise-looking dates get pasted into migration tickets and stop being guesses.

New to the calendar

OpenSSL 3.0 — 7 September 2026 (source). The LTS branch that a great many distributions and appliances quietly link against. The date is upstream’s, not necessarily yours — RHEL and Ubuntu LTS backport past it — but after it, nobody upstream is looking at 3.0 at all. Worth auditing what your base images actually contain.
MongoDB 8.2 — 31 July 2026 (source). Ten days out. 8.2 was a rapid release, not a long-term one, and the short leash was always part of the deal. If you are on it without having chosen the rapid track deliberately, 8.0 is the version you meant.
RabbitMQ 4.2 — 31 July 2026 (source). Community support only; commercial extended support runs to 2030. A support matrix showing “2030” reads as reassurance, and for paying customers it is. For everyone else the number is next Friday.
Windows 11 24H2 — 13 October 2026 (source). Home and Pro only; Enterprise and Education get another year. Same build, same version number, two clocks. Mixed estates are where this bites — the retail laptops and contractor machines that never went through imaging.

Changed

Nothing. Tonight was the pipeline’s first run, so it has no previous values to compare against yet — every item is “new” by definition. From tomorrow, moved dates become detectable, and a date quietly sliding from November to January is the single most useful thing this archive can tell you.

Housekeeping

The calendar still contains a handful of illustrative sample entries from the pre-launch build, visibly marked as such. They come out as real entries replace them, and the site stays out of search engines until they are gone.

One pipeline note in the interest of showing the workings: 49 of 50 sources fetched clean, one failed on a bad identifier in our own config. Fixed tomorrow, logged tonight.