Minimus is shutting down its hardened container image registry — reg.mini.dev goes dark on 22 October, with the maintenance clock starting today

After two quiet nights, a real one: Minimus — a hardened, near-zero-CVE container image provider in the same category as Chainguard and Docker Hardened Images — is ending operations. Its registry, reg.mini.dev, is turned off on 22 October 2026 after a 60-day maintenance period that begins today, 24 August. Images you have already pulled keep working, but no further patched images are published, so anything pinned to Minimus stops getting the security updates that were the whole reason to use it. Meanwhile the late-August cluster is now imminent: the OpenAI Assistants API removal is two days out (26 August) and a four-way pile-up lands on the 31st. All eleven sub-30-day entries were re-checked against their sources tonight and hold.

After two honest-quiet nights, tonight has a real entry — and it is one for anyone who hardens their container builds.

New: Minimus is winding down — reg.mini.dev closes 22 October

Minimus sells hardened, minimal container images: stripped-down, near-zero-CVE drop-in replacements for standard base and application images, in the same category as Chainguard Images and Docker Hardened Images. In an official notice on minimus.io, the founders say the current business and investment climate has left the company “unable to continue operations.”

Two dates matter. Today, 24 August, starts a 60-day maintenance period — bug fixes, commercial support, and images kept current with upstream updates. On 22 October 2026, Minimus ceases operations and turns off its registry, reg.mini.dev. Images you already pulled keep working, but no new or patched images ship after that — so anything pinned to Minimus quietly stops receiving the security updates that were the entire point. Enterprise Edition customers get individual outreach from 24 August about winding down their contracts, refunds included.

The fix is a base-image migration with a security deadline: find every Dockerfile, compose file, and pipeline that pulls from reg.mini.dev, then repoint to Chainguard Images, Docker Hardened Images, Google distroless, or your own Wolfi/-slim bases and rebuild before the cutoff. Hardened images differ in their users, shells, and bundled certs, so leave time to re-test.

The late-August cluster is now imminent

The seven-deadlines-in-six-days stretch flagged last night has arrived at the front of the countdown:

26 August (two days) — the OpenAI Assistants API is removed. Move /v1/assistants, /v1/threads, and /v1/runs calls to the Responses API first.
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, not 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: 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). All eleven entries within 30 days were re-checked against their primary sources tonight and all hold — including the Sentinel 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.