Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Hotfixes a bug where Drupal CMS Olivero 1.2.6 pretended to be 1.x-dev, which confused Composer and could prevent sites from requiring or updating packages.
If you are getting errors like this:
drupal/drupal_cms_olivero is fixed to 1.x-dev (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Then try updating to this version, using these commands:
This release tries to preserve bare-bones compatibility with Canvas -- i.e., you should not get a white screen of death if you install Canvas whilst using this theme -- but that needs more work and testing.
Hotfix release to correct a bug that causes configuration validation to fail when applying a recipe that uses this theme (the olivero_footer_menu block has an invalid setting).
Fixed a bug that broke Canvas when this theme was installed: #3548837: Remove Canvas-incompatible SDCs. Although Drupal CMS Olivero will not officially support Canvas, we do want to allow Canvas to be installable alongside it.
This is mostly a maintenance release of Drupal CMS. There aren't too many user-facing changes, but there are some under-the-hood enhancements to make life easier in the future, clear the way for Drupal CMS to be truly multilingual, and increase compatibility with more hosting platforms. This version also requires Drupal core 11.2, which has its own set of shiny new things.
We fixed bugs too, but almost all of those bug fixes are also in the 1.0.x releases, so take a look at those for more details.
Recipes have no update path; the change records provide instructions to make manual configuration changes to an existing Drupal CMS site. You do NOT need to make these changes if you don't want to; your site will continue working as it currently does.
Recipes have no update path, so instructions are provided for manually making the appropriate configuration changes to address certain bugs. You do NOT need to make these changes if you don't want to; your site will continue working as it currently does.
See the change records for information on the configuration changes that have been made in this version, and how you can implement them on your Drupal CMS site.