- Issue created by @Project Update Bot
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.1 & MySQL 5.7last update
8 months ago Waiting for branch to 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
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.1 & MySQL 5.7last update
8 months ago Waiting for branch to pass - 🇮🇳India ankitv18
ankitv18 → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to Needs work
3 months ago 6:58am 3 September 2024 - Status changed to Needs review
3 months ago 7:28am 3 September 2024 - Status changed to RTBC
3 months ago 7:39am 3 September 2024 - First commit to issue fork.
- Status changed to Fixed
3 months ago 12:30pm 4 September 2024 -
wells →
committed 47da63ea on 4.0.x authored by
ankitv18 →
Issue #3434674: Automated Drupal 11 compatibility fixes for social_api
-
wells →
committed 47da63ea on 4.0.x authored by
ankitv18 →
- 🇮🇳India ankitv18
@wells I guess you have missed out to give the credit to the members.
- 🇺🇸United States wells Seattle, WA
Yeah, sorry about that. I'm still getting used to the new MR merge flow. Will correct on the other ecosystem module work. Thanks for contributing!
- 🇺🇸United States wells Seattle, WA
Ah, there we go -- flipping the status with the proper checks appears to have worked.
Automatically closed - issue fixed for 2 weeks with no activity.