The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
The module currently declares core_version_requirement: ^9.3 || ^10, so it cannot be installed on Drupal 11. Drupal 10 reaches end-of-life on 9 December 2026 — the same day Drupal 12.0.0 is released — so Contribute needs a release that supports Drupal 11 today and is already clean for Drupal 12.
This is the tracking (meta) issue for that work on a new 2.0.x branch (^10.3 || ^11). It supersedes the stale automated Drupal 10 patches (#3411691: Automated Drupal 10 compatibility fixes, #3286765: Automated Drupal 10 compatibility fixes) and resolves "No supported release" (#3418296: No supported release).
Proposed resolution
Create a 2.0.x branch supporting ^10.3 || ^11 and address the following:
- Bump
core_version_requirementandcomposer.jsonto^10.3 || ^11, dropping Drupal 9 (EOL). - Add
TypedConfigManagerInterfaceto theConfigFormBaseconstructor, required since Drupal 10.2 / 11. - Convert the
@Blockannotation to a#[Block]PHP attribute (Drupal 12 prep — annotations are being removed). - Code-quality fixes: correct the
hook_install()docblock, fix thecase 'user';semicolons and the:href_ groupsplaceholder space in ContributeManager. - Convert README.txt to README.md (closes #3320697: Replace README.txt with README.md, currently RTBC).
- Add
.gitlab-ci.ymlwith next-major (Drupal 11) testing enabled. - Fix the drupal.org integration: the autocomplete controller and the functional test use dead Drupal 7-era drupal.org endpoints. Rework them against current APIs and re-green the tests on Drupal 11.
- Tag
2.0.0-beta1.
Remaining tasks
- Close #3439382: I have created views wanted to filter the content based on the taxonomy displayed on the result. But filter taxonomy is taking only 10 row values. (misfiled support request against a non-existent
8.x-5.0-beta3version). - Close #2942882: Backport to Drupal 7? (Drupal 7 backport — Drupal 7 is EOL).
- Keep feature requests #2948780: Show information about the themes and modules, #2944871: Add tracking code to Contribute Module and #2944296: Display maintainers/contributors for installed projects open for after 2.0.0.
Comments
Comment #3
joshua1234511The Drupal 11 readiness work is complete on the 2.0.x branch and the pipeline is green.
Summary of what landed:
core_version_requirement/composer.jsonto^10.3 || ^11(Drupal 9 dropped, EOL).TypedConfigManagerInterfaceto theConfigFormBaseconstructor (required since Drupal 10.2 / 11).@Blockannotation to a#[Block]PHP attribute (Drupal 12 prep).Request::get()deprecation, removed dead code (getPerson()/getPeople()), and cleaned up minor bugs..gitlab-ci.yml, converted README.txt and CHANGELOG.txt to Markdown, removed the stale RELEASE-NOTES.md, and made CSpell/PHPStan/Stylelint all pass.I verified the module end to end on a local Drupal 11.3 site: the status report section and the Community Information block both render with live Drupal.org data, and the settings form saves correctly.
I don't have release permissions on this project. Could a maintainer (@adriancid / @jrockowitz) please create a release from
2.0.x? This also resolves "No supported release" (#3418296: No supported release).Suggested approach:
2.0.x-devbranch release now, so people can test on Drupal 11.2.0.0-beta1as the first adoptable pre-release, then promote to2.0.0when ready.Happy to help with anything needed to get the release out.
Comment #4
joshua1234511Comment #6
joshua1234511Comment #7
joshua1234511