Problem/Motivation

Since there is already a branch for Drupal 10, the 2.0.x branch should require Drupal 11.3 as minimum Drupal version.

Proposed resolution

Make the 2.0.x branch require Drupal 11.3 or higher versions.

Issue fork seven-3559555

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

avpaderno created an issue. See original summary.

avpaderno opened merge request !233

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Needs work
Issue tags: -Needs change record

  • avpaderno committed 3eb76cea on 2.0.x 
    Issue #3559555: Require Drupal 11.3 as minimum Drupal version
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: avpaderno » Unassigned
Status: Needs work » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

macdev_drupal’s picture

macdev_drupal commented

Hi,
I noticed that the 2.0.x branch now requires Drupal 11.3 as the minimum version, and that several relatively substantial changes were made at the same time (e.g. removal of seven.theme, various refactorings and deprecation fixes).

Since Seven is officially in maintenance-only mode, and Drupal 11.2 is still supported until June 2026, I’m a bit surprised by the early bump to 11.3 and the amount of internal changes.

Is this technically required due to new APIs/deprecations in 11.3, or is there a broader direction beyond minimal maintenance?

We still use Seven for some existing installations and would like to understand whether more structural changes are expected in the 2.0.x branch, or if this was a one-off update to ensure compatibility with 11.3.

Thanks for the clarification!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Maintenance fixes only includes the changes necessary to make the theme compatible with latest or currently supported Drupal versions.

I choose Drupal 11.3 because it is easier to make the theme compatible with Drupal 11.3 than with Drupal 11.1 and Drupal 11.3. Drupal 11.3 introduced a big change for themes, as theme_get_setting() has been deprecated.

No new features will be implemented.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

stefan.korn’s picture

stefan.korn
Primary language German
Location Jossgrund
commented

So there is no current release of seven that supports Drupal 11.2 (although Drupal 11.2 will be supported until 06/26), 2.0.0-beta2 is the last version to support 11.2?

Though the deprecation workaround for theme_get_settings seems still be present in 2.0.0-beta3: https://git.drupalcode.org/project/seven/-/blob/a8d3e59cfab111df280b15e2...

So beta3 could technically still run with 11.2, only the version constraint is blocking?