Problem/Motivation

Maintaining support for older versions of PHP and Drupal core holds us back from using APIs and language features that save time. It also costs the module's (volunteer) maintainers time and energy to maintain support for older systems.

At time-of-writing (2026-05-06), Feedback's 3.x branch claims to support all versions of Drupal 9, all versions of Drupal 10, and all versions of Drupal 11.

But at time-of-writing, all versions of Drupal 9, Drupal 10.0 through 10.4, as well as 11.0, and 11.1 have all been deprecated and don't receive support (including security support) from the Drupal community. Further, Drupal 12 is scheduled to release this year.

Also, since the Gitlab Templates project's #3463894: Update templates so 11.0 is the default/current branch was merged, we no longer have a way to test whether the Feedback module still works on Drupal 9. That is to say, from a regression-testing standpoint, we already do not support these versions.

Note that dropping compatibility with an unsupported version of Drupal core is allowed for minor versions of a module, but feedback is currently in alpha, which means the API (and what we support) can be unstable.

Proposed resolution

Change the core_version_requirement lines in our .info.yml files to core_version_requirement: ^10.5 || ^11.2, i.e.: dropping support for older versions of Drupal core.

As a work-around, my understanding is that the mglaman/composer-drupal-lenient plugin can be used to install Feedback on an older site if absolutely necessary.

Remaining tasks

  1. Merge request - merge request !17 created by @mparker17 in #2
  2. Feedback from users of the module
  3. Commit
  4. Release

User interface changes

None.

API changes

No changes to Feedback's API.

Data model changes

None.

Issue fork feedback-3588867

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

mparker17 created an issue. See original summary.

mparker17 opened merge request !17

mparker17’s picture

mparker17
he/him
Primary language English
Location UTC-5
commented
Issue summary: View changes
Status: Active » Needs review

Merge request !17 created.

I would like feedback from active users of the module if possible! I'm open to maintaining support for old versions of Drupal core within a reasonable time limit... please do speak up if - for example - you need D10.4 support for another year.

But, if I don't hear anything in 4 or 5 weeks, then I'm going to assume that everyone's already using a supported version of Drupal core and therefore nobody has any issues with this proposal (i.e.: merge the issue as-is and include this in the first beta release).