Machine-readable lifecycle data for the Maintenance and Release Schedule wiki

Hi — your Maintenance and Release Schedule wiki tracks each major's release and end-of-life dates by hand (492 revisions and counting). Keeping that table current is exactly the kind of thing that quietly drifts.

We publish the same data as free JSON, no key needed:

curl https://api.endoflife.ai/v1/product/nextcloud

Right now it returns 34 → EOL 2027-06-30 (latest 34.0.2), 33 → 2027-02-28 (33.0.7), 32 → 2026-09-30 (32.0.13) — matching your current table.

It's sourced from project announcements and re-verified against primary sources (methodology); 100 requests/day per IP unauthenticated, which is plenty for a build step or a cached page. You could render the wiki table from it, or use it as a drift cross-check on the hand-maintained one.

Entirely up to you whether it's useful — no follow-up either way. A link back is welcome but genuinely optional. Happy to answer questions about the endpoint here.

Start with the Maintenance and Release Schedule wiki and inspect the endoflife.ai JSON endpoint to understand the available lifecycle fields and how they match the current table. Decide whether the integration should render the wiki data or provide a drift check; done means the schedule stays aligned with the published lifecycle dates without requiring manual updates.