- 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 Needs review
about 1 year ago 6:03am 25 March 2024 - First commit to issue fork.
- 🇺🇸United States papagrande US West Coast
Blocked by https://www.drupal.org/project/eloqua_api_redux/issues/3454756 📌 Drupal 11 compatibility fixes for eloqua_api_redux Needs review
-
papagrande →
committed 445b7317 on 2.0.x authored by
project update bot →
Issue #3435634 by papagrande: Automated Drupal 11 compatibility fixes...
-
papagrande →
committed 445b7317 on 2.0.x authored by
project update bot →
- 🇮🇳India vinayakmk47
Hello, Thank you for providing the automated patch and details regarding Drupal 11 compatibility. I have manually tested the changes and verified that the module works as expected with Drupal 11. Automated tests were also run successfully.
The patch #2 updates the info.yml file and other compatibility changes correctly align with Drupal 11 requirements. Marking this issue as Reviewed and Tested by the Community. 🎉
check the before and after screenshot.
- 🇮🇳India vinodhini.e chennai
Applied the patch #2 and successfully installed the module on Drupal 11.0.1.
Attached the screenshot for reference.
Thanks for the patch!
- 🇺🇸United States papagrande US West Coast
I forgot to mark this as fixed after I merged the MR yesterday.
Thank you for the reviews, but when reviewing patches and merge requests, you must also review the code for quality and test the functionality to confirm that no regressions are introduced.
- 🇮🇳India vinayakmk47
Thank you for the update and for marking this issue as fixed. I appreciate your reminder about reviewing code quality and testing functionality during the review process. Ensuring no regressions are introduced is indeed critical, and I’ll make sure to keep this in mind for future reviews.
Automatically closed - issue fixed for 2 weeks with no activity.