Problem/Motivation
Drupal CMS is currently built against Drupal 10.3
The target release date for a Drupal CMS 1.0 release is January 15th 2025, which is more than a month after Drupal 11.1.
It would be good to synchronise the versions, so that Drupal CMS releases on the most recent version of Drupal core, there are several reasons for this:
1. If it's on any previous version, it will look weird.
2. If it's on any previous version, users who install Drupal CMS will immediately be faced with updating to a new Drupal major release, which is non-trivial especially with no Drupal experience.
3. Drupal 11.1 is the most realistic target for any blocking core issues for Drupal CMS to be applied - e.g. everything can get into 11.1, but not everything can get into 10.4.x and 11.0.x depending on what it is.
🐛
Recipes' imported config is validated too strictly by default
Active
is fixed against 10.4.x, but still patched in Drupal CMS because it's on 10.3.x, and some other issues might only land in 11.1.
4. There are currently several core patches applied:
https://git.drupalcode.org/project/drupal_cms/-/blob/0.x/drupal_cms_patc...
It's my understanding that Drupal CMS will ship with automatic updates enabled, and automatic updates does not allow updates when the composer patches plugin is in the code base, unless it has been put there on the command line by the site owner. Therefore, a stable release of Drupal CMS can have composer patches, or it can have automatic updates, but it cannot have both. The target audience for Drupal CMS should and cannot be expected to untangle patches themselves so even if there was some way to have both, it would not be a good experience when people actually try to update and find they have patches that don't apply in composer.patches.json (hopefully because they already got fixed, but worse if they didn't and need rebasing).
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
