- Issue created by @project update bot
- last update
10 months ago 6 pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- last update
10 months ago 6 pass - First commit to issue fork.
This MR!9 makes the module compatible with D11. I have also added SS.
- First commit to issue fork.
- 🇮🇳India shashi_shekhar_18oct
MR!9 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1
- Status changed to Needs work
19 days ago 4:44am 10 January 2025 - 🇺🇸United States dillix
@manishvaity you should change:
core_version_requirement: ^8 || ^9 || ^10 || ^11
to:
core_version_requirement: ^8.8 || ^9 || ^10 || ^11
- 🇺🇸United States dillix
I fixed all issues including right gitlab-ci.yml, tests, phpcs and phpstan warnings. Now MR goes green.
- First commit to issue fork.
-
acbramley →
committed 659f38a0 on 2.x authored by
project update bot →
Issue #3433565 by dillix, manishvaity, acbramley: Automated Drupal 11...
-
acbramley →
committed 659f38a0 on 2.x authored by
project update bot →
Automatically closed - issue fixed for 2 weeks with no activity.