- Issue created by @Project Update Bot
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
6 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 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, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
6 months ago Waiting for branch to pass - 🇳🇱Netherlands Watergate
Watergate → changed the visibility of the branch 3429627-automated-drupal-11 to hidden.
- 🇳🇱Netherlands Watergate
Watergate → changed the visibility of the branch 3429627-automated-drupal-11 to active.
- 🇳🇱Netherlands Watergate
We dropped support for the 1.0.x branch and created the 2.x branch. The latter is compatible with Drupal 10 and Drupal 11.
- Status changed to Active
6 months ago 12:23am 19 March 2024 - 🇳🇱Netherlands Watergate
Watergate → changed the visibility of the branch project-update-bot-only to hidden.
- 🇳🇱Netherlands Watergate
Watergate → changed the visibility of the branch 3429627-automated-drupal-11 to hidden.
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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Status changed to Needs review
3 months ago 11:26pm 17 June 2024 -
Watergate →
committed 7bca7c97 on 2.x authored by
Project Update Bot →
Issue #3429627 by Watergate: Automated Drupal 11 compatibility fixes for...
-
Watergate →
committed 7bca7c97 on 2.x authored by
Project Update Bot →
- Status changed to Active
3 months ago 8:20pm 20 June 2024 - 🇳🇱Netherlands Watergate
Watergate → changed the visibility of the branch project-update-bot-only to hidden.