Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇷🇸Serbia bojanz
@mishradeepak1991 I have no clue what you're doing. All code posted to this issue was already committed.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇦🇺Australia VladimirAus Brisbane, Australia
Needs fixing
- phpstan (next major)
- phpunit (next major)
- 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3429855-automated-drupal-11 to hidden.
- 🇮🇳India Rajeshreeputra Pune
The 'Next major' test is currently failing due to jQuery UI's incompatibility with Drupal 11 and jQuery UI Draggable has dependency on it, as detailed in issue 📌 Automated Drupal 11 compatibility fixes for jquery_ui Needs review . Once the necessary updates are merged and released, we should see the test start running successfully.
- 🇮🇳India Rajeshreeputra Pune
The 'Next major' test is currently failing due to jQuery UI's incompatibility with Drupal 11, as detailed in issue 📌 Automated Drupal 11 compatibility fixes for jquery_ui Needs review . Once the necessary updates are merged and released, we should see the test start running successfully.
- @rajeshreeputra opened merge request.
- First commit to issue fork.
- @rajeshreeputra opened merge request.
- First commit to issue fork.
- @deepakkm opened merge request.
- First commit to issue fork.
- @rajeshreeputra opened merge request.
- First commit to issue fork.
- last update
about 11 hours ago 1 fail - 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3430237-automated-drupal-11 to hidden.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 11 hours ago Waiting for branch to pass - last update
about 11 hours ago 1 fail - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 12 hours ago Waiting for branch to pass - last update
about 12 hours ago 1 fail - last update
about 12 hours ago 1 fail - @rajeshreeputra opened merge request.
- First commit to issue fork.
-
alexpott →
committed 321fc72c on 1.0.x authored by
Project Update Bot →
Issue #3428766 by alexpott: Drupal 11 compatibility
-
alexpott →
committed 321fc72c on 1.0.x authored by
Project Update Bot →
- 🇬🇧United Kingdom alexpott 🇪🇺🌍
alexpott → changed the visibility of the branch 3428766-automated-drupal-11 to hidden.
- First commit to issue fork.
-
rattusrattus →
committed 38d373bc on 1.0.x
Issue #3428281: Automated Drupal 11 compatibility fixes for book_pdf
-
rattusrattus →
committed 38d373bc on 1.0.x
-
rattusrattus →
committed 0a91d8c7 on 1.0.x
Issue #3428252: Automated Drupal 11 compatibility fixes for book_pdf
-
rattusrattus →
committed 0a91d8c7 on 1.0.x
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 14 hours ago Waiting for branch to pass -
jsacksick →
committed e137d4c3 on 8.x-2.x authored by
Project Update Bot →
Issue #3438230: Automated Drupal 11 compatibility fixes for...
-
jsacksick →
committed e137d4c3 on 8.x-2.x authored by
Project Update Bot →
- last update
about 14 hours ago 160 pass - First commit to issue fork.
- @deepakkm opened merge request.
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 17 hours ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 18 hours ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
about 18 hours ago Waiting for branch to pass -
acbramley →
committed e0bd1707 on 2.x
Issue #3429862: D11 support
-
acbramley →
committed e0bd1707 on 2.x
- 🇦🇺Australia acbramley
acbramley → changed the visibility of the branch 3429862-d11-compatibility-fixes to hidden.
-
jrglasgow →
committed 776cac2e on 8.x-1.x authored by
Project Update Bot →
Issue #3438154: Automated Drupal 11 compatibility fixes for autologout
-
jrglasgow →
committed 776cac2e on 8.x-1.x authored by
Project Update Bot →
- last update
1 day ago 1 pass, 2 fail - Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7last update
1 day ago Not currently mergeable. - @japerry opened merge request.
- First commit to issue fork.
- @japerry opened merge request.
- First commit to issue fork.
- @vishalkadam opened merge request.
- 🇮🇳India vishal.kadam Mumbai
vishal.kadam → made their first commit to this issue’s fork.
- 🇮🇳India naveenvalecha New Delhi
Postponed on 📌 Automated Drupal 11 compatibility fixes for jquery_ui Needs review
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Reviewed, tested on a D11-alpha1 site, missing fixes manually added.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Balu Ertl → changed the visibility of the branch project-update-bot-only to hidden.
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
1 day ago Waiting for branch to pass - @balu-ertl opened merge request.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Balu Ertl → made their first commit to this issue’s fork.
-
japerry →
committed 50b09db6 on 8.x-1.x authored by
Project Update Bot →
Issue #3429630: Automated Drupal 11 compatibility fixes for core_context
-
japerry →
committed 50b09db6 on 8.x-1.x authored by
Project Update Bot →
- last update
1 day ago 18 pass - last update
1 day ago 18 pass - last update
1 day ago 18 pass - last update
1 day ago 18 pass - First commit to issue fork.
-
japerry →
committed 10799157 on 8.x-2.x authored by
ankitv18 →
Issue #3431931: Automated Drupal 11 compatibility fixes for memcache
-
japerry →
committed 10799157 on 8.x-2.x authored by
ankitv18 →
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Reviewed, tested on a D11-alpha1 site, missing fixes manually added.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Balu Ertl → changed the visibility of the branch project-update-bot-only to hidden.
- last update
1 day ago 9 pass - last update
1 day ago 9 pass - @balu-ertl opened merge request.
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Balu Ertl → made their first commit to this issue’s fork.
-
Greg Boggs →
committed af5f827b on 1.0.x authored by
Project Update Bot →
Issue #3448859: Automated Drupal 11 compatibility fixes for...
-
Greg Boggs →
committed af5f827b on 1.0.x authored by
Project Update Bot →
- 🇺🇸United States Greg Boggs Portland Oregon
Greg Boggs → made their first commit to this issue’s fork.
- 🇨🇦Canada tbradbury
I added a change to make field type categories compatible with Drupal 11: https://git.drupalcode.org/project/json_field/-/merge_requests/22/diffs?...
See the change record: https://www.drupal.org/node/3375748 → .
This doesn't change the issue status since CI should still come first.
- last update
1 day ago 15 pass - 🇨🇦Canada tbradbury
travis-bradbury → made their first commit to this issue’s fork.
-
kevinquillen →
committed 828b4010 on 8.x-2.x authored by
Project Update Bot →
Issue #3431868: Automated Drupal 11 compatibility fixes for...
-
kevinquillen →
committed 828b4010 on 8.x-2.x authored by
Project Update Bot →
- last update
1 day ago 3 pass - First commit to issue fork.
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8last update
1 day ago Waiting for branch to pass - @rajeshreeputra opened merge request.
-
prudloff →
committed 01ada0d3 on 1.x authored by
Project Update Bot →
Issue #3448826: Automated Drupal 11 compatibility fixes for...
-
prudloff →
committed 01ada0d3 on 1.x authored by
Project Update Bot →
- First commit to issue fork.
- 🇮🇳India deepakkm
created a new ticket to fix phpunit previous major issue on drupal 9 - https://www.drupal.org/project/password_policy/issues/3449074 📌 PHPunit test failing for Drupal 9 Needs work
-
just_like_good_vibes →
committed c2e6ee4a on 1.0.x
#Issue #3448883: Drupal 11 compatibility (+ small improvements)
-
just_like_good_vibes →
committed c2e6ee4a on 1.0.x
- @just_like_good_vibes opened merge request.
- First commit to issue fork.
- last update
1 day ago 120 pass - last update
1 day ago 62 pass - 🇮🇳India vishalkhode
The below two tests were failing:
1) Drupal\Tests\entity_clone\Functional\EntityCloneCloneableEntitiesConfigTest::testCloneableEntitiesConfigForm Test was run in child process and ended unexpectedly 2) Drupal\Tests\entity_clone\Functional\EntityCloneParagraphTest::testParagraphClone Test was run in child process and ended unexpectedlyAfter debugging, found that the issue was in search_api module and created ticket: 🐛 PHP Fatal error: Declaration of Drupal\search_api_db\Plugin\search_api\backend\Database::__sleep() must be compatible Needs review for the same. After applying the patch and re-running the tests in local for Entity Clone module, can confirm all tests are passing.
- 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
Let's first get 📌 Add GitLab CI template Needs review in, so that we can observe the tests passing on Drupal 11 and require tests to pass on "the next major"? 😊
- 🇦🇺Australia sime Canberra
Just :array type hinting. I successfully ran code that touches UpdateFixtureSubscriber.
- @acbramley opened merge request.
- 🇦🇺Australia acbramley
acbramley → changed the visibility of the branch 2.x to hidden.
-
acbramley →
committed 396b432a on 8.x-1.x authored by
ankitv18 →
Issue #3429862 by ankitv18, Berdir, acbramley, Rajeshreeputra: Automated...
-
acbramley →
committed 396b432a on 8.x-1.x authored by
ankitv18 →
-
ramlev →
committed 9e40e6d5 on 1.0.x authored by
Project Update Bot →
Issue #3448888: Automated Drupal 11 compatibility fixes for wayf
-
ramlev →
committed 9e40e6d5 on 1.0.x authored by
Project Update Bot →
- First commit to issue fork.
- 🇦🇺Australia acbramley
Thanks for all the work here, we've got green tests for next major and minor and only a small number of phpstan failures on next major which we're ignoring for now (these can be fixed in a follow up but is not a priority).
Here's what I settled on:
- Fail phpcs/phpstan on current version
- Allow failures on next major/minor for phpstan
- Run tests on next major/minor
- Turn off SYMFONY_DEPRECATIONS_HELPER on next major
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to active.
- 🇦🇺Australia acbramley
acbramley → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
-
VladimirAus →
committed 7fb9c753 on 3.0.x authored by
Project Update Bot →
Issue #3434356 by Project Update Bot, jannakha: Automated Drupal 11...
-
VladimirAus →
committed 7fb9c753 on 3.0.x authored by
Project Update Bot →
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇦🇺Australia acbramley
@ankitv18 those changes were for Drupal 8, we don't support Drupal 8 anymore.
I'm find this hard to follow as questions are being asked and then more changes are being pushed.
I do not feel like we need to run tests on previous minor/major. This is just busywork maintenance to keep the tests working. For a module that's already undermaintained for how widely it is used, I would prefer to not have this overhead.
CORE_PREVIOUS_PHP_MIN: 8.1
I've bumped the minimum PHP already on 8.x-1.x to 8.1, is this still needed?
Basically, I agree with #31
- First commit to issue fork.
- last update
2 days ago 32 pass - last update
2 days ago 2 pass - last update
2 days ago 2 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
2 days ago Waiting for branch to pass - Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
2 days 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
2 days ago 6 pass - last update
2 days ago 6 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 🇮🇳India vishalkhode
@Rajeshreeputra Reviewed MR and changes looks good to me.
@WalkingDexter: If your plan is to make a new major release support starting from Drupal Core 10.1.x or If plan is to make a patch release for the same reason, then we can merge the changes. If not, then we need to add the
DeprecationHelperclass in the module itself, so that it works on Drupal Core 9.3.x as well. - @project-update-bot opened merge request.
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.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- 🇮🇳India vishalkhode
vishalkhode → made their first commit to this issue’s fork.
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @ankitv18 opened merge request.
- First commit to issue fork.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Issue created by @Project Update Bot
- 🇮🇳India ankitv18
With these changes https://www.drupal.org/project/diff/issues/3406873 📌 Adopt GitlabCi Fixed Previous minor and major version of phpunit will fail.
It would be good if maintainer decide what could be the next steps:- Whether to include OPT_IN_TEST_PREVIOUS_MINOR and OPT_IN_TEST_PREVIOUS_MAJOR in the gitlab and revert the changes made in the tests files which is pushed in a issue#3406873 📌 Adopt GitlabCi Fixed
- Or include D11 and issue#3406873 📌 Adopt GitlabCi Fixed in the 2.x branch 📌 Cut a 2.x branch Active
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
2 days ago 3 pass, 2 fail - @idebr opened merge request.
- First commit to issue fork.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- @project-update-bot opened merge request.
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.ymlfile 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- 🇮🇳India Rajeshreeputra Pune
Additionally, any errors from the validate step should be fixed.
- PHPCS: Fixed warnings.
- Eslint: We will retain this for the maintainer to take appropriate action.
- PHPStan: Already appended the 'ignore next line' directive, but it appears to be non-functional.
- 🇮🇳India vishalkhode
Looks like there are couple of tests failures and deprecations and those needs to be fixed.
- last update
2 days ago 47 pass - @deepakkm opened merge request.
- last update
2 days ago 32 pass - last update
2 days ago 32 pass - last update
2 days ago 32 pass - 🇨🇭Switzerland Berdir Switzerland
> CORE_PREVIOUS_PHP_MIN: 8.1
That's a neat idea, but there are tons of test fails on previous major and some on previous minor too. Can't commit like this. Either we need to remove previous minor/major testing or we could also set them to allow failure, then we could at least manually verify if there are *new* changes if we want to, but also seems like a waste of resources. Decision for @acbramley to make.
> Could we consider enabling PHPStan checks on the next major version? While it's understandable that we might encounter some failures, setting it to 'allow failure' could still be beneficial. This way, we can ensure it runs and provides us with valuable insights.
I believe it is not useful. The insights are for the pretty far future, nothing we need to fix now. That said, my proposal is to not commit with next minor/major testing anyway and only do that on a weekly schedule, so it won't run in on merge requests either way. Again. decision for @acbramley.
- First commit to issue fork.
- First commit to issue fork.
- 🇮🇳India vishalkhode
The CI for previous major is failing. Can we get that fixed ? Looks like adding following variable would fix the issues:
variables: CORE_PREVIOUS_PHP_MIN: 8.1 - 🇦🇺Australia acbramley
The baseline changes are to fix failures that also happened on the current branch, not just next
Yes but then it started failing phpstan. HEAD was updated and fixed to include this with the PHP 8.1 requirements.
- 🇯🇵Japan ptmkenny
@godotislate on Slack suggested that the loop could be caused by this: [#3177901]
- 🇷🇺Russia WalkingDexter
I'm not sure about these changes:
- https://git.drupalcode.org/project/simple_sitemap/-/merge_requests/90/di...
- https://git.drupalcode.org/project/simple_sitemap/-/merge_requests/90/di...
They need to be carefully reviewed. At least there is no need to change the file mode. Additionally, any errors from the validate step should be fixed.
- @ankitv18 opened merge request.
- 🇯🇵Japan ptmkenny
Upgrade Status now shows only a single Drupal 12 deprecation, which is marked ignore for now:
web/modules/json_field/src/Element/JsonText.php: +--------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | status | line | message | +--------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ignore | 14 | Class Drupal\json_field\Element\JsonText extends deprecated class Drupal\Core\Render\Element\RenderElement. Deprecated in drupal:10.3.0 and is removed from drupal:12.0.0. Use Drupal\Core\Render\Element\RenderElementBase instead. | +--------+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+So I think this is ready for consideration.
- 🇨🇭Switzerland Berdir Switzerland
> The current MR also introduces new failures on the current major with the baseline changes so back to NW.
The baseline changes are to fix failures that also happened on the current branch, not just next. Those changes apparently happen due to phpstan and related dependency updates.
- 🇯🇵Japan ptmkenny
Added an MR with initial support for Drupal 11. Once 📌 Add GitLab CI template Needs review gets added this will be easier to test.
- last update
4 days ago 15 pass - @ptmkenny opened merge request.
- First commit to issue fork.
- 🇮🇳India Rajeshreeputra Pune
For phpcs issue/warnings fixes please see 📌 Fix phpcs issue/warnings. Needs work .
- last update
4 days ago 32 pass - last update
4 days ago 32 pass - last update
4 days ago 5 pass, 2 fail - last update
4 days ago 32 pass - last update
4 days ago 47 pass, 1 fail - last update
4 days ago 47 pass, 1 fail - last update
4 days ago Composer require-dev failure - 🇦🇺Australia acbramley
As discussed in slack, I'd like to keep enforcing phpstan passing. As a maintainer, I'd rather the MR pipeline fail outright than having to check every time if any regressions have been introduced there. The problem is now of course that the next major runs are failing because, well, code is deprecated there that isn't in our current major. It makes no sense to me to fail phpstan on next major.
The current MR also introduces new failures on the current major with the baseline changes so back to NW.
- 🇯🇵Japan ptmkenny
I'm having trouble determining why there are so many errors like this:
1) Drupal\Tests\datetime_testing\Kernel\PinnedTimeTest::testDecoration Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "cache_factory", path: "cache_factory -> datetime_testing.test_time -> state -> cache.bootstrap -> cache_factory".These appear in 10.3 (PHPUnit 9) and 11 (PHPUnit 10), but not 10.2. Why?
- last update
4 days ago 51 pass - last update
4 days ago 51 pass - last update
4 days ago 51 pass - @ptmkenny opened merge request.
- First commit to issue fork.
- 🇨🇭Switzerland Berdir Switzerland
I had also fixed an incorrect merge for phpcs/phpstan allow failure override.
But now that is actually failing on both current and next minor/major versions. I removed the loadRevision() false positives from the baseline, but next minor/major have deprecations too. It would probably be possible to add deprecation helper calls to remain compatible back at least to 10.1, with corresponding phpstan ignore comments if necessary, or it might be possible to override next major/minor phpstan jobs to allow failures again, but personally I think that's not really worth the effort.
- 🇨🇭Switzerland Berdir Switzerland
I updated the .gitlab-ci.yml so that next major testing is working, which essentially means running concurrent tests through run-tests.sh (which is much faster too) and the deprecation workaround until #3400979: Is SYMFONY_DEPRECATIONS_HELPER: weak correct for contrib deprecation testing needs? → is merged and available.
That resulted in some test fails, which I fixed (old config schema for sequences and a removed views key). With that, phpunit (next major) is now green.
Previous minor is failing, somehow there's a difference in core whether it shows closed or hidden, didn't investigate. I prefer keeping previous minor testing on so I can ensure that there are no regressions with still-supported minor versions, but seems a bit tedious to handle that. Could be re-enabled after 10.3 is out. Removed that for now, see https://git.drupalcode.org/issue/diff-3429862/-/jobs/1626487 for the test fail.
As for next minor/major testing, my approach for that is to remove that from the default config before committing the D11 merge requests and then setting up a weekly schedule with that on. The idea is that I test as much backward as possible as merge requests might break that. But it's quite unlikely that merge requests break forward compatibility. Instead, that happens due to core changes, so the weekly test informs me if that starts to fail (although next major is set to allow failure, that could be overridden I guess). The plan is a bit work in progress. But that's up to the maintainer to decide how to merge this.
Would be great to get this in so I can proceed with 📌 Add support for Drupal 11 Needs review without having to add workarounds (as it as a require-dev on diff module).
- First commit to issue fork.
- last update
6 days ago 32 pass - 🇮🇳India gg24
The latest MR and patch looks good. I tested it locally and applied rector as well. No new changes. All works fine and compatible with D11. Hence moving it to RTBC.
Thanks!
- last update
7 days ago Composer require failure
