Changelog

You're looking at it. This page tracks what ships on drupalreleases.com, newest first, with the history back to the very first deploy filled in retroactively. New entries land here with each release.

Two new entry points for browsing: an index of every tracked project and an index of every detected ecosystem, both built to be crawled as well as browsed.

Also in this batch: the AI summary queue now works through its backlog instead of only summarizing new arrivals, and release charts label their months correctly at month boundaries.

The biggest data expansion so far: the importer now reads each release's .info.yml and composer.json from git.drupalcode.org, so the site knows what every release depends on and which Drupal core versions it supports.

• Project pages show compatibility insights — which core versions a project is ready for, grouped by core support cycle.
• Release pages list per-release dependencies as collapsible cards, and dependency changes between releases show up in the updates timeline.
• Historical releases were backfilled from the drupal.org release-history feed, so compatibility data reaches years back.

Every stable Drupal core release now has its own page — release notes context, support window, and where it sits in its branch — starting from the Drupal hub.

• Support windows are visualized as timelines instead of table rows.
• Hub pages chart release activity and answer their search intent with dynamic titles and descriptions.
• Structured data (JSON-LD) expanded across the home, hub, and project pages, and the sitemap carries real last-modified dates.
• Edge cache lifetimes are now tiered per route, and the cache is purged only when data actually changes.

You can now search every tracked project straight from the site header.

• Project pages swapped abstract cadence and stability stats for concrete maintenance signals — how actively a project is being looked after.
• The banner reselects hourly using recency-decayed importance, so stale items rotate out on their own.
• Release timelines render as stacked bars, dates settled on one unambiguous format, and the stack moved to Laravel 13 and Tailwind CSS 4.

Project pages often opened with a wall of maintainer-written markup. Each project now gets a short AI-generated summary of what it actually does, generated from its drupal.org description — the full original description stays available verbatim.

The Drupal, CMS, and ecosystem pages also received proper descriptions and meta tags, and the stack moved to PHP 8.4.

Related projects now cluster into ecosystems — Commerce, Webform, AI, and friends — detected automatically from shared project-name prefixes rather than maintained by hand.

• Each ecosystem gets its own page with stats, releases, and scoped updates.
• The updates timeline gained filters styled as a toggle bar, and the homepage a recent-updates block.
• The site banner now picks its items by importance scoring instead of plain recency.

A new updates timeline turns raw imports into a readable stream of what happened across the Drupal ecosystem, and the most important items surface in a banner at the top of every page.

• Every data change — a new release, a metadata change — now generates an update entry through an event-driven pipeline.
• The site sits behind Cloudflare's edge cache, so pages load fast from anywhere and survive traffic spikes.
• The JSON API gained rate limiting and input validation, and "modules" became "projects" across the site (old /module/… links redirect).

Tracking now covers the whole contrib space: themes and distributions joined modules, each with release timelines of their own.

Under the hood the admin panel, login, and user accounts were removed entirely. Every page is public and anonymous — which is what makes the aggressive edge caching that came next possible.

The site now tracks contributed modules, not just core. Modules are imported from drupal.org with their full release history, site-usage counts, and security-advisory coverage.

• Module listings show usage counts, a security coverage badge, and a "Most Used" tab.
• Every module gets a detail page with its description, release history, activity metrics, and a release timeline chart.
• A sitemap.xml went up, and the whole site got a responsive pass — mobile menu, stacking footer, and a proper Drupal droplet favicon.

You no longer have to visit the site to know something shipped:

• An RSS feed announces new stable releases as they are imported.
• A small JSON API exposes version and release data for scripts and dashboards.
• Release tables gained tabbed views with search, color-coded support status, and a "time remaining" column for every support window.

The first version of drupalreleases.com is up: a single overview of Drupal core and PHP versions with their support windows, so you can see at a glance which versions are still supported and when the next end-of-life date lands.

Version data is imported on a schedule from drupal.org and endoflife.date, and only stable releases make the list.