Sub-modules are not marked as Drupal 11 ready, which causes Upgrade Status to get confused

Created on 13 August 2025, 4 days ago

Problem/Motivation

Upgrade Status is showing me this with 4.10:

The incompatible column is "Local 11-ready" and the compatible one is "Drupal.org 11-ready", which seemed really odd, and I downloaded the module again with Composer to make sure nothing was modified in my local copy. After that, I dug through the code and realized that the sub-modules were the cause for the discrepency because their info files weren't updated to include Drupal 11 support.

Steps to reproduce

See above.

Proposed resolution

Update version constraints of sub-modules to allow Drupal 11.

Remaining tasks

Do the thing.

User interface changes

None.

API changes

None.

Data model changes

None.

🐛 Bug report
Status

Active

Version

4.0

Component

Code

Created by

🇨🇦Canada ambient.impact Toronto

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024