What's new on drupalreleases.com

Search can now be narrowed by security advisory coverage, development status (under active development, maintenance fixes only, no further development, obsolete) and topic category such as Media, Multilingual or E-commerce, and sorted by name as well as by installs. Project pages show the development status and link each topic to the matching search. Status and topics are filled in from drupal.org over the next day as projects are refreshed, and the select menus now have a proper down arrow.

The same filters work in the MCP server: search-projects takes category, development_status, maintenance_status and security_coverage, can browse by them without a search term, and both it and get-project now return each project's development status and topics.

A short message now sits under the header on every page: use direct release data with your AI assistant. Its Copy prompt button copies a prompt you paste into your assistant; the prompt explains the MCP server and walks the assistant through installing it. It replaces the scrolling updates banner, and the latest updates remain on the updates page.

The MCP server page now sits at the same address you add to your assistant, so the URL you paste is the page that explains it. The old /mcp-server address redirects there. The page also leads with how to connect, then example questions and a table of the tools.

The MCP server now has its own page. It covers what the server is, what you can ask your AI assistant with it, and how to connect it in about a minute. There's also a look at how the data is ingested from drupal.org, enriched, and served. The page is linked from the main navigation.

Search now looks beyond project names. It also reads each project's plain-language summary, so a search for "spam protection" or "image carousel" finds modules whose names don't say it.

• Filter results by Drupal core version, project type, and maintenance status (active, slowing, dormant). You can also filter without typing a search term, for example to list every active Drupal 11 theme.
• Exact and leading name matches still come first, so searching for a machine name like webform works as before.
• Matches found through the summary are ranked by relevance and install base.

AI assistants such as Claude can now look up drupalreleases.com data directly through a Model Context Protocol server. Sign in with a one-time email link to create an access token, then add the server to your assistant. There's no password to set.

• Search projects by name or machine name, ranked by install base.
• Get a project with its latest stable release, Drupal core compatibility, PHP requirement, maintenance status, recent releases, and dependencies.
• Drupal and PHP support shows which versions still get security updates, and until when.
• Recent updates from the timeline, filterable by update type or project.

The server is read-only, and every answer links back to the page it came from.

A new PHP versions page answers the question every upgrade starts with: which PHP version does this Drupal version need, and how long is that PHP release supported?

• Supported PHP versions with their active-support and security-fix windows, from endoflife.date.
• A matrix of every Drupal release cycle against the supported PHP versions, using the requirement Drupal core declares in its composer.json.

Each Drupal core release cycle now has its own page, such as Drupal 11.4, answering the questions people actually search for: when it was released, when active support and security coverage end, what the latest release is, and which PHP version it needs.

• The Drupal versions overview, the homepage timeline, and every release page link through to the cycle pages.
• Drupal core releases now carry their PHP requirement, read from core/composer.json like contrib releases read theirs.

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.