- Issue created by @project update bot
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
- Status changed to RTBC
8 months ago 8:01am 9 August 2024 -
Anybody →
committed c2fe6b00 on 2.0.x authored by
Project Update Bot →
Issue #3433583: Automated Drupal 11 compatibility fixes for node_class
-
Anybody →
committed c2fe6b00 on 2.0.x authored by
Project Update Bot →
- Status changed to Fixed
8 months ago 10:13am 9 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India ajay gadhavana
I tried to update the module version, add a license file, and correct the incorrect hook implementation comments.
I requested the module owner to accept this patch and deploy it so that others using Drupal 11 can easily benefit from this module. If you don’t have time, please add me as a maintainer so I can push updates and make necessary changes whenever required.