Install

To start a new Drupal project with version 11.0.0:

To update your site and all dependencies to the latest version of Drupal:

To update your site to this specific release:
Pinning to a specific release may make it more challenging to update your site in future, see composer documentation for managing pinned versions

Using Composer to manage Drupal site dependencies

Downloads

Download drupal-11.0.0.tar.gztar.gz 18.07 MB
MD5: 1cf81680a1a288eb705edcbf3527f21a
SHA-1: a4eb030e66073a59629d1b24e4dcb360e90654c2
SHA-256: d40fef2b241424ad57715cfcd756fe74e81bc0039e29b77371058af9bc056453
Download drupal-11.0.0.zipzip 30.42 MB
MD5: e7d4f9f9eeab7b85d8100485065666e2
SHA-1: 201e6fb5397de4d352eb88fc880d58aac4a076b6
SHA-256: 63b5807017bac1fe3ea3ce95a1f65313fa6a4e8bc28f05086c9e89090b614860

Release notes

This is the first supported release of the new Drupal 11 major version, and it is ready for use on production sites! Learn more about Drupal 11 and the Drupal core release cycles.

Learn more about Drupal 11.0.0

Drupal 11.0.0 follows shortly after the Drupal 10.3.0 release. Drupal 10.3 has most of the new functionality that Drupal 11 does, but retains backwards compatibility layers added through Drupal 10.3.0's release. Sites must update to Drupal 10.3 before updating to Drupal 11.

If you are starting a new Drupal project, you have a choice between Drupal 10.3 and 11, and generally should choose Drupal 11 where possible for forward compatibility with future releases.

Regardless of which version you choose now, new features will only be added to Drupal 11 minor releases. Plan to adopt Drupal 11 so that you can easily update to Drupal 11.1 and later.

Refer to the guide Upgrading Drupal for how to perform a major version upgrade. Preparing your site for an upgrade describes tools you can use to check the Drupal 11 compatibility of modules, themes, and sites.

Both 11.0.0 and 10.3.2 (the latest Drupal 10 release) include all the latest improvements, and they have the same public APIs and features aside from a few edge-cases. This also means modules and themes can be compatible with Drupal 10 and 11 at the same time! The key changes in 11.0.0 are:

  1. Deprecated code, including entire modules and themes, has been removed.
  2. Dependencies have been updated to new major versions as appropriate.
  3. Platform requirements (including supported PHP and database versions, Composer requirements, and supported browsers) have been updated.

For all other changes, refer to the 10.3.x branch.

Important update information

Sites must update to the latest release of 10.3 before upgrading to Drupal 11

Drupal sites running 10.2 or earlier versions must first update to 10.3.0 or later before updating to Drupal 11. All core updates added before 10.3.0 have been removed. In general, sites should update core and contributed modules to the most recent releases available for their current major core version, before updating to the next major release.

A new API has been added to support backports of database updates across major and minor versions. This primarily affects core development, but might also be needed for contributed projects (since core will support two major versions simultaneously going forward).

Changes to site-owner-managed files

Platform requirements changes

PHP requirements

Database requirements

The requirements for the database drivers supported by Drupal 11 are:

  • The MySQL database driver requires MySQL 8.0.
  • The MariaDB database driver requires MariaDB 10.6.
  • The PostgreSQL database driver requires PostgreSQL 16.
  • The SQLite database driver requires SQLite 3.45 with the json1 extension.

Web server

Support for IIS is removed. Sites using IIS are encouraged to change to a supported web server. Drupal 11 does not provide a web.config file. We encourage bug reports for issues that may affect web servers other than IIS.

Browser support changes

See the browser support policy for more information.

Removed functionality

The following pages have been removed without replacement:

  • The "Add new module" page at /admin/modules/install
  • The "Add new theme" page at /admin/theme/install
  • The "Add new module or theme" page at /admin/reports/updates/install

Using Composer is the only way to safely and correctly add new code to a Drupal installation. See the Additional information, deprecations, and API changes for installing an extension through the user interface.

Multiple core modules have been removed from core and moved to contributed projects

Numerous modules and themes have been removed from Drupal core and moved to contributed projects. In many cases, the removed extensions have little to no impact on site development.

Sites should check their installed modules against the following list, and either uninstall the module or require the contributed version prior to upgrading to Drupal 11. If a removed module is required for a site's functionality, the contributed version should be downloaded to the codebase or added to the Composer requirements prior to upgrading. Do not uninstall the module, since this would destroy the module configuration.

Drush may bypass warning and error messages on update.php related to missing modules or themes. The status report will display errors about missing modules after upgrading.

Backend (PHP) dependency changes

Added PHP dependencies

  • A dependency on doctrine/lexer 2.0 is added. Previously, the dependency was implied as a dependency of doctrine/annotations.

  • A Composer dependency on ext-zlib has been added. (This PHP extension was already a required part of Drupal's PHP configuration, but previously, the dependency was not correctly declared.)

Updated PHP dependencies

  • Symfony has been upgraded to 7.1.1.

  • Doctrine Annotations has been updated from 1.14.3 to 2.0.1.

  • PHPUnit has been upgraded from 9.5 to 10.5. Test developers should refer to the changes required for PHPUnit 10 compatibility for a summary of the breaking changes and details of how to update their tests for PHPUnit 10.

  • Drupal core's Composer development dependency has been updated to Composer 2.7.7, which addresses security vulnerabilities. It is recommended that Drupal site owners also update their local Composer versions with composer self-update.
  • Numerous other dependencies have received minor- and patch-level updates to the latest versions.

  • Twig has been upgraded from 3.5.0 to 3.9.3. If you have custom code that extends Twig, you should read the Twig v3.9.0 changelog as there are new deprecations.

Frontend (CSS and JavaScript) dependency changes

Removed frontend dependencies

Updated frontend dependencies

Known issues

PHP 8.4 compatibility for Drupal 10 and 11 remains under development. 11.1 (or possibly a patch release of 11.0) will provide full compatibility with PHP 8.4.

Search the issue queue for known issues.

All changes since 11.0.0-rc1

What’s next?

  1. Learn how to install Drupal
  2. Learn how to update Drupal
  3. Extend Drupal to do more
  4. Get training
  5. Check out what others built
Created by: catch
Created on: 2 Aug 2024 at 05:45 UTC
Last updated: 5 Aug 2024 at 22:18 UTC
Bug fixes
New features
Insecure
Unsupported

Other releases