The densest day on the calendar: four sunsets land at once — Adobe Lightroom API, CoScreen, MongoDB 8.2, RabbitMQ 4.2

Four dated items reach their sunset on the same day — the most this calendar has tracked at once. The Adobe Lightroom API reaches end-of-life, Datadog shuts down CoScreen entirely, and two runtime support windows close: MongoDB 8.2 and RabbitMQ 4.2 community support. Nothing new or changed across the fifty monitored feeds tonight beyond far-future version tables; the story today is the dates already on the calendar coming due.

Some nights the value of a shutdown calendar is a new discovery. Tonight it is the opposite: four dates we have been counting toward all arrive on the same day. 31 July is the densest single day this calendar has tracked — an API end-of-life, a full product shutdown, and two runtime support windows closing, all at once. Every one was written and verified in advance, and every one was re-checked against its primary source tonight and found unchanged. This is the calendar doing exactly what it is for.

Passing today

Adobe Lightroom API (source) — today, 31 July, the Lightroom API (Firefly Services) reaches end-of-life. Adobe directs remaining callers to Photoshop API v2 and warns of “service disruptions” for integrations not moved by now. This is a hard cutoff, not a soft deprecation, and v2 is a different API — a real migration, not a base-URL swap.
CoScreen (source) — today, 31 July, Datadog discontinues CoScreen entirely. The product — not a feature — shuts down, with no named successor and no migration path. Teams that relied on its multi-cursor remote control (each participant with a real cursor and keyboard) lose the one capability the obvious substitutes do not reproduce.
MongoDB 8.2 (source) — today, 31 July, the 8.2 rapid release leaves support: no further patches, including security patches. If you took 8.2 for a specific feature rather than deliberately choosing the rapid track, 8.0 (long-term, supported to 2029-10-31) is the version to be on.
RabbitMQ 4.2 (source) — today, 31 July, community support for the 4.2 series ends: no more free releases, including security fixes. Commercial extended support runs to 2030 — a support matrix showing “2030” is reassurance for paying customers only. Open-source users should upgrade to 4.3 (community support to 30 November 2026).

All four entry statuses have been moved to passed.

Still counting down

Everything below is already on the calendar and was re-checked against its primary source tonight — all unchanged:

ChatGPT Atlas browser — 9 August, export your data first.
Rails 7.2 — 9 August, end of security support.
Relay — 15 August, the app shuts down.
Google Content API for Shopping — 18 August, end-of-life.
OpenAI Assistants API — 26 August, removed from the API.
New Relic drop-filter-rules API — 31 August, the API endpoint is removed.
OpenSSL 3.0 — 7 September, the LTS branch stops receiving fixes.
OpenAI Sora 2 video API — 24 September, the models and Videos API are removed.

Further out, Windows 11 24H2 end of servicing (13 October) and the OpenAI legacy audio/realtime models (20 January 2027) are on the calendar too. The full list lives on the calendar.

From the monitored feeds

Nothing publishable tonight. The fifty monitored sources surfaced only version-EOL rows from an aggregator (Redis point releases, most of them years out) — not a primary source, so not something we publish as fact, and firmly the territory of the version-EOL reference tables that already exist. The discovery scan turned up one shutdown with real discussion — a single Mastodon community instance winding down — which is a genuine loss for the people on it but sits outside what this calendar tracks: developer APIs, products, and software with a migration path. So tonight’s substance is the four dates coming due, not anything new. That is a normal, healthy night for a calendar whose job is to record dates in advance and then be right when they arrive.