- Issue created by @project update bot
- last update
9 months ago Patch Failed to Apply 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
9 months ago 7:42pm 24 March 2024 - last update
9 months ago 37 pass - First commit to issue fork.
- last update
9 months ago Composer require-dev failure - 🇳🇱Netherlands megachriz
Alright, tests cannot run on Drupal 11 yet until the Token module is declared compatible with Drupal 11.
- Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7
50:34 50:34 Queueing 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-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
- Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7
50:19 50:19 Queueing The last submitted patch, 7: nopremium.1.x-dev.rector.patch, failed testing. View results →
- last update
6 months ago 37 pass - last update
6 months ago 37 pass - last update
6 months ago 32 pass, 2 fail - last update
6 months ago 32 pass, 2 fail - last update
6 months ago 32 pass, 2 fail - last update
6 months ago 32 pass, 2 fail - last update
6 months ago 32 pass, 2 fail -
MegaChriz →
committed 49762e22 on 8.x-1.x
Issue #3433627 by MegaChriz, Project Update Bot: Added support for...
-
MegaChriz →
committed 49762e22 on 8.x-1.x
- Status changed to Active
6 months ago 9:36am 26 June 2024 - 🇳🇱Netherlands megachriz
Alright, all checks pass on GitLab CI and all tests pass on Drupal 11. I merged the code.
Setting status back to "Active" for possible new automated D11 compatibility fixes.