- 🇺🇸United States bradjones1 Digital Nomad Life
Merged the PU bot proposal. As there was no other substantive work done here, no other credit.
-
bradjones1 →
committed c75d7d4a on 8.x-1.x authored by
Project Update Bot →
Issue #3431475 by bradjones1: Automated Drupal 11 compatibility fixes...
-
bradjones1 →
committed c75d7d4a on 8.x-1.x authored by
Project Update Bot →
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States jrglasgow Idaho
according to my testing it appears to be working
- 🇨🇦Canada joseph.olstad
This can simmer in the 8.x-2.x branch for a while, the merge commit was squashed.
-
joseph.olstad →
committed 95606b94 on 8.x-2.x authored by
jrglasgow →
Issue #3430553 by Project Update Bot, jrglasgow, joseph.olstad, Berdir:...
-
joseph.olstad →
committed 95606b94 on 8.x-2.x authored by
jrglasgow →
- @japerry opened merge request.
- First commit to issue fork.
- 🇺🇸United States DamienMcKenna NH, USA
Nothing else to worry about for now.
- @jrglasgow opened merge request.
- First commit to issue fork.
Automatically closed - issue fixed for 2 weeks with no activity.
- @jrglasgow opened merge request.
- First commit to issue fork.
- 🇩🇪Germany Anybody Porta Westfalica
Someone should please test, if further code changes are required.
- First commit to issue fork.
- 🇮🇳India chandu7929 Pune
I think there is only pending item : https://www.drupal.org/project/scheduler/issues/3451750 📌 Fix: The update to convert "numeric" arguments to "entity_target_id" is deprecated Needs review
Automatically closed - issue fixed for 2 weeks with no activity.
-
jsacksick →
committed 5f7ac91e on 3.x authored by
vishalkhode →
Resolve #3438428 "Automated drupal 11"
-
jsacksick →
committed 5f7ac91e on 3.x authored by
vishalkhode →
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India chandu7929 Pune
Hello @geek-merlin → Can you please help with merge and release this?
- 🇮🇳India vipin.mittal18 Greater Noida
Fixes are working perfectly on Drupal version 11.0.0-rc1. Refer below screenshot
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India chandu7929 Pune
There are conflicts, need to resolve and push should do the job.
- 🇮🇳India chandu7929 Pune
Once we merge change of 3463494-inline-entity-form 📌 Gitlab PHPunit job at Next Major needs D11-compatible test dependencies Fixed it will start running test on next major.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
📌 Add gitlabci Active Not prepared to mark this without tests, so did that instead
-
larowlan →
committed 79475577 on 8.x-1.x authored by
Project Update Bot →
Issue #3434037: Automated Drupal 11 compatibility fixes for...
-
larowlan →
committed 79475577 on 8.x-1.x authored by
Project Update Bot →
- First commit to issue fork.
- 🇬🇧United Kingdom jonathan1055
MR141 was created against the 4.4.x-1-x branch, which was compatible with Drupal 4. The last commit was 18 years ago!
I have opened #3451507: Project Update Bot created MR against a 4.x branch from Drupal 4 - last commit 18 years ago → in the project issue queue just for fun, to see what response there is.
-
vvuksan-fastly →
committed 7a10862c on 4.0.x-dev
Issue #3451071: Automated Drupal 11 compatibility fixes for fastly
-
vvuksan-fastly →
committed 7a10862c on 4.0.x-dev
- 🇺🇸United States joelsteidl
2.x is no longer maintained.
The JWT app type will be deprecated. We recommend that you create Server-to-Server OAuth or OAuth apps to replace the functionality of a JWT app in your account. See the JWT app type migration guide for details.
On June 1, 2023, Developers will not be able to create new JWT app types.
On September 1, 2023, Zoom will disable JWT app type authorization. Contact Developer Support for details. -
Damien Laguerre →
committed d2a666d0 on 4.x
Issue #3448715: Automated Drupal 11 compatibility fixes for ipless
-
Damien Laguerre →
committed d2a666d0 on 4.x
-
phenaproxima →
committed 0c83bb61 on 3.1.x authored by
Project Update Bot →
Issue #3459557: Automated Drupal 11 compatibility fixes for...
-
phenaproxima →
committed 0c83bb61 on 3.1.x authored by
Project Update Bot →
-
Damien Laguerre →
committed 346540c5 on 2.0.x
Issue #3428932: Automated Drupal 11 compatibility fixes for axeptio
-
Damien Laguerre →
committed 346540c5 on 2.0.x
- First commit to issue fork.
-
szeidler →
committed 5a1c20ff on 2.0.x authored by
Project Update Bot →
Issue #3431891: Automated Drupal 11 compatibility fixes for...
-
szeidler →
committed 5a1c20ff on 2.0.x authored by
Project Update Bot →
- @idebr opened merge request.
- First commit to issue fork.
- 🇮🇳India Bhanu951
Bhanu951 → changed the visibility of the branch 3437552-fixes-for-opt-in-for-security-review to hidden.
- @bhanu951 opened merge request.
- First commit to issue fork.
- @chandu7929 opened merge request.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
- First commit to issue fork.
- @megachriz opened merge request.
- First commit to issue fork.
- 🇳🇱Netherlands MegaChriz
I've looked through all the changes and made a few minor changes a few hours ago. The code prior to these last changes have been running 2 to 3 days on four D10 sites and I haven't catched any regressions yet.
So I'm merging this now!
Not creating a new release yet, because I think 3 days is too short for catching regressions. Also, I like to see 📌 Support Drush 12 and above only Active and 📌 PHPunit Next Major pipeline failure Active to be resolved before the next release. And it would be good to test Feeds manually on a D11 site.
But at least by merging this, modules that extend Feeds can be made compatible with D11 too.
Thanks all!
The issue is left open to allow the update bot to post new fixes, should there be any.
-
MegaChriz →
committed 6ca6ac32 on 8.x-3.x authored by
ankitv18 →
Issue #3430449 by ankitv18, deepakkm, Project Update Bot, MegaChriz,...
-
MegaChriz →
committed 6ca6ac32 on 8.x-3.x authored by
ankitv18 →
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India vishalkhode
vishalkhode → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇱Israel jsacksick
None of the changes look like breaking changes, so we can probably make the changes in both branches actually. I said we should target 3.x without looking at the changes, my bad. Surprised these are the only changes required :).
Let's address the points I raised, then we can merge this, though I haven't been actively maintaining IEF, so perhaps geek-merlin would like to do that?
- 🇮🇳India chandu7929 Pune
The 3.x branch currently supports Drupal 8.8 and above, so I've not removed it as part of this ticket. I've just included the D11 support in the core_version_requirement from ^8.7.7 || ^9 || ^10 to ^8.8 || ^9 || ^10 || ^11. The reason of updating ^8.7.7 to ^8.8 to reflect it's same in the composer.json.
ok, then lets include previous minor/major CI.
- First commit to issue fork.
- @ankitv18 opened merge request.
- First commit to issue fork.
- First commit to issue fork.
- 🇮🇳India vishalkhode
@ufku: Looks like we've missed merging schema changes and it's causing our PHPUnit tests to fail. Ref: 🐛 missing schema exception in Drupal 11 Active : Can we please get that merged ?
- 🇺🇸United States micahw156
Marking this duplicate of 📌 Preparing for Drupal 11 Active . I will perform needed updates manually.
Automatically closed - issue fixed for 2 weeks with no activity.
- First commit to issue fork.
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Thanks for retesting and providing more information. I probably won’t be able to look at this until next Tuesday or Wednesday. Feel free to ping me after that if I haven’t responded by Thursday next week.
- 🇮🇳India vishalkhode
@jsacksick All tests are passing and CI is green now. Can you please review & merge the changes ?
- 🇮🇳India vishalkhode
@Rajeshreeputra @bohart Can we please get a stable/RC release for the same ? Thanks.
- 🇮🇳India vishalkhode
@chandu7929: The 3.x branch currently supports Drupal 8.8 and above, so I've not removed it as part of this ticket. I've just included the D11 support in the
core_version_requirement
from^8.7.7 || ^9 || ^10
to^8.8 || ^9 || ^10 || ^11
. The reason of updating^8.7.7
to^8.8
to reflect it's same in the composer.json. - 🇮🇳India chandu7929 Pune
Vishal, if we are panning to provide support from 8.8 then we should update CI to check on lower version as well.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India chandu7929 Pune
I think we should support D11 in the 3.x branch, that makes more sense to me so we can discontinue the 1.x branch
I agree with you.
- 🇮🇳India vishalkhode
Hi @jsacksick
Yes, that completely makes sense to me if we are planning to discontinue 1.x branch, then yes we shouldn't merge this in 1.x branch. I'm creating another MR against 3.x branch and let's see if all tests are passing, then you can go ahead review and merge the changes.I think we should support D11 in the 3.x branch, that makes more sense to me so we can discontinue the 1.x branch.
- 🇪🇸Spain marcoscano Barcelona, Spain
OK, all green, I'm merging this.
Thanks again for working on this! Automatically closed - issue fixed for 2 weeks with no activity.
-
marcoscano →
committed 84e644ce on 8.x-2.x authored by
Balu Ertl →
Issue #3430263 by Berdir, Balu Ertl, marcoscano: Automated Drupal 11...
-
marcoscano →
committed 84e644ce on 8.x-2.x authored by
Balu Ertl →
-
mabho →
committed 8bfb6fed on 1.0.x authored by
Project Update Bot →
Issue #3451389 by Project Update Bot, mabho: Automated Drupal 11...
-
mabho →
committed 8bfb6fed on 1.0.x authored by
Project Update Bot →
- 🇧🇷Brazil mabho Rio de Janeiro, RJ
Besides the automated update performed by the automated tool, there was a need to fix the code in
src/Form/SettingsForm.php
because of this error message being thrown in Drupal 11:ArgumentCountError: Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct(), 1 passed in /var/www/web/modules/custom/visual_debugger/src/Form/SettingsForm.php on line 31 and exactly 2 expected in Drupal\Core\Form\ConfigFormBase->__construct() (line 43 of /var/www/web/core/lib/Drupal/Core/Form/ConfigFormBase.php).
I applied an update to fix this problem. There was a need to incorporate variable
Drupal\Core\Config\TypedConfigManagerInterface
to the constructor method ofConfigFormBase
. - First commit to issue fork.
- 🇮🇱Israel jsacksick
I think we should support D11 in the 3.x branch, that makes more sense to me so we can discontinue the 1.x branch.
Thoughts here? - 🇮🇳India ankitv18
Changes looks good and pipelines are executed a successful jobs, hence marking this one as RTBC
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India vipin.mittal18 Greater Noida
Hello Kristen,
How are you doing?
Despite my best efforts, I was unable to reproduce the issue again, even after a fresh installation with Drupal 11.0.0-rc1. This issue appears not to exist, as my colleagues also tried to replicate it. Therefore, I believe we can release a Drupal 11 compatible stable version of password policy. Apologies for any disruption.
An animated GIF is created as a reference to indicate that there are no more warnings being logged
- 🇪🇸Spain marcoscano Barcelona, Spain
Thank you for working on this! 🙏
I agree on the testing strategy you mentioned. Just removed the next minor/major and added the scheduled pipeline to be run weekly (thanks for the suggestion).
However, this run now failed, with error:There was 1 failure: 1) Drupal\Tests\entity_usage\Functional\Update\UpdateTest::testUpdate8206 Failed to run installer database tasks: Database drupal not found. The server reports the following message when attempting to create the database: SQLSTATE[HY000]: General error: 1007 Can't create database 'drupal'; database exists., Failed to CREATE a test table on your database server with the command CREATE TABLE {drupal_install_test} (id int NOT NULL PRIMARY KEY). The server reports the following message: SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected: CREATE TABLE "test56035940drupal_install_test" (id int NOT NULL PRIMARY KEY); Array ( ) .Are you sure the configured username has the necessary permissions to create tables in the database? /builds/project/entity_usage/web/core/tests/Drupal/FunctionalTests/Update/UpdatePathTestBase.php:226 /builds/project/entity_usage/web/core/tests/Drupal/FunctionalTests/Update/UpdatePathTestBase.php:141 /builds/project/entity_usage/web/core/tests/Drupal/FunctionalTests/Update/UpdatePathTestBase.php:113 /builds/project/entity_usage/web/core/tests/Drupal/Tests/BrowserTestBase.php:367 /builds/project/entity_usage/web/core/tests/Drupal/FunctionalTests/Update/UpdatePathTestBase.php:92 /builds/project/entity_usage/tests/src/Functional/Update/UpdateTest.php:41 /builds/project/entity_usage/vendor/phpunit/phpunit/src/Framework/TestResult.php:729 FAILURES! Tests: 1, Assertions: 1, Failures: 1. ---- Drupal\Tests\entity_usage\Functional\EntityUsageLayoutBuilderTest ----
Does this ring any bell for you? Has anything changed in CI between yesterday and today? :) 🤔
- First commit to issue fork.
- 🇬🇷Greece vensires
Thank you everyone for your work! The changes seem working so it's good to be RTBC by me. The only unresolved thread is regarding the `.gitlab-ci.yml` variables.
I just want to add some really kind and gentle pressure on this in order to say that websites using this module (32500+ currently) will not be able to upgrade to Drupal 11 without a stable version containing these changes. Drupal Lenient composer plugin won't solve the problem since we still have the dependency issue coming from the
"symfony/mailer": "^5.3 || ^6.0"
requirement and Lenient only fixes "drupal/core" requirements.A possible workaround I have found is to change my
composer.json
'srepositories
property to the following, while also adding the diff from the MR as patch of course:{ "type": "package", "package": { "version": "1.4.2", "name": "drupal/symfony_mailer", "description": "Symfony Mailer", "type": "drupal-module", "license": "GPL-2.0-or-later", "require": { "html2text/html2text": "^4.0.1", "symfony/mailer": "^5.3 || ^6.0 || ^7.1@beta", "tijsverkoyen/css-to-inline-styles": "^2.2" }, "extra": { "drush": { "services": { "drush.services.yml": "^11" } } } } }, { "type": "composer", "url": "https://packages.drupal.org/8" }
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇬🇧United Kingdom jonathan1055
I have created a separate issue 📌 Gitlab PHPunit job at Next Major needs D11-compatible test dependencies Fixed which can be committed first. Then we can properly test the other D11 issue.
Thanks to @vishalkhode for providing the alternative repo info. Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India Rajeshreeputra Pune
Changes looks good, however I don't see CI running for Drupal 11, please add next major support in gitlab CI.
- @ankitv18 opened merge request.
- @rajeshreeputra opened merge request.
- First commit to issue fork.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch project-update-bot-only to hidden.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India ankitv18
ankitv18 → changed the visibility of the branch project-update-bot-only to hidden.
-
joegraduate →
committed 3ff93db3 on 2.0.x authored by
Project Update Bot →
Issue #3428559 by Project Update Bot, joegraduate: Automated Drupal 11...
-
joegraduate →
committed 3ff93db3 on 2.0.x authored by
Project Update Bot →
- First commit to issue fork.
-
heddn →
committed 87e23ab0 on 8.x-1.x authored by
Project Update Bot →
Issue #3430360 by heddn, Project Update Bot: Automated Drupal 11...
-
heddn →
committed 87e23ab0 on 8.x-1.x authored by
Project Update Bot →
- First commit to issue fork.
-
heddn →
committed f225efe8 on 8.x-1.x authored by
Project Update Bot →
Issue #3429108 by Project Update Bot, heddn: Automated Drupal 11...
-
heddn →
committed f225efe8 on 8.x-1.x authored by
Project Update Bot →
- First commit to issue fork.
-
heddn →
committed ec92253e on 1.0.x authored by
Project Update Bot →
Issue #3451888 by Project Update Bot, heddn: Automated Drupal 11...
-
heddn →
committed ec92253e on 1.0.x authored by
Project Update Bot →
- First commit to issue fork.
- @jrglasgow opened merge request.
- First commit to issue fork.
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
Thanks for testing. If there are warnings, they should be fixed first please. Moving back to needs work.
- First commit to issue fork.
- 🇺🇸United States greggles Denver, Colorado, USA
There were some fails on this MR, but I think both of those are unrelated and are fixed on other recent issues, so this can be merged as is.
Thanks, Bot!
Leaving open in case any more changes come along as being needed.
-
greggles →
committed 340e9e56 on 8.x-1.x authored by
Project Update Bot →
Issue #3435270: Automated Drupal 11 compatibility fixes for user_expire
-
greggles →
committed 340e9e56 on 8.x-1.x authored by
Project Update Bot →
- First commit to issue fork.
- 🇨🇭Switzerland Berdir Switzerland
Did quite a bit of work on this. Tests are all green now on all enabled core versions.
* Opt-in for next minor and major, previous minor and concurrent testing (speeds up phpunit job from 5min to 2min). Personally, I recommend removing next minor/major testing from CI, because it's unlikely that merge requests will break future versions (unlike previous minor (and major, once D11 is out), instead, what I do is set up a "next" weekly schedule with both of those enable, because if things break here it's because core changes.
* Workaround for mysql errors around triggers with DER, should be fixed in gitlab templates soon as well.
* workarounds for testing on next major with various test dependencies that aren't compatible yet
* Various test fixes, mostly those tests already failed at least since 10.3 too
* Removed image_upload test config, it's disabled anyway but caused weird schema errors.
* reduced previous changes around entity storage and also logging. really no need to have an exception *and* an assert() and a @var docblock. Seems fair to have an assert, but a revisionable entity type must have a revisionable storage or it would not work at all. Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
-
heddn →
committed e7c513ff on 8.x-1.x authored by
Project Update Bot →
Issue #3429204 by Project Update Bot, heddn: Automated Drupal 11...
-
heddn →
committed e7c513ff on 8.x-1.x authored by
Project Update Bot →
-
japerry →
committed 3eec8b01 on 8.x-1.x authored by
Balu Ertl →
Issue #3434339 by ankitv18, japerry, Balu Ertl: Automated Drupal 11...
-
japerry →
committed 3eec8b01 on 8.x-1.x authored by
Balu Ertl →
- heddn Nicaragua
Tests are failing on errors around
EntityReferenceTestTrait
. We also might want to just set the minimum Drupal core version to 10.1 and remove some of the BC logic in the latest MR. That said, I'll let another maintainer comment about jumping the minimum supported version. - First commit to issue fork.
- @goz opened merge request.
- First commit to issue fork.
- 🇮🇳India vipin.mittal18 Greater Noida
There is warnings
Warning: Undefined array key "character_length" in Drupal\password_policy_length\Plugin\PasswordConstraint\PasswordLength->validateConfigurationForm() (line 130 of /home/ide/project/docroot/modules/contrib/password_policy/password_policy_length/src/Plugin/PasswordConstraint/PasswordLength.php)
on saving "character length" password constraint but can be ignored for this ticket as restriction works perfectly.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India chandu7929 Pune
Vishal, lets add next major CI as well to see what failing on D11
- First commit to issue fork.
- 🇮🇳India vipin.mittal18 Greater Noida
vipin.mittal18 → changed the visibility of the branch 3433859-automated-drupal-11 to active.
- 🇮🇳India vipin.mittal18 Greater Noida
vipin.mittal18 → changed the visibility of the branch 3433859-automated-drupal-11 to hidden.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India Rajeshreeputra Pune
The changes look good, have been verified, and are working as expected. I will proceed with the merge, and we look forward to a release soon with a stable D11-compatible version.
-
Rajeshreeputra →
committed 9c6ed46a on 2.2.x authored by
deepakkm →
Issue #3434204: Automated Drupal 11 compatibility fixes for...
-
Rajeshreeputra →
committed 9c6ed46a on 2.2.x authored by
deepakkm →
- First commit to issue fork.
- First commit to issue fork.
- 🇮🇳India vishalkhode
Hi @jonathan1055
Thanks for the reply. Included two more tickets for separate fixes required for Drupal 11 compatibility.
Separate issues are used for the actual fixes.
I've cherry-picked commit from all these tickets which are required to make module Drupal 11 compatible and also added one temp commit: 47066616 to run tests on Drupal 11 and you can see all PHPUnit tests are passing (https://git.drupalcode.org/issue/scheduler-3434325/-/pipelines/230921) except following deprecation errors which are not related to Scheduler module.
-
The update to convert "numeric" arguments to "entity_target_id" for entity reference fields for view "scheduler_scheduled_content" is deprecated in drupal:10.3.0 and is removed from drupal:12.0.0
. The above will be fixed in 📌 Fix: The update to convert "numeric" arguments to "entity_target_id" is deprecated Needs review
-
"Drupal\entity\EventSubscriber\EntityDuplicateSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
"Drupal\entity\EventSubscriber\EntityDuplicateSubscriber" now to avoid errors or add an explicit @return annotation to suppress this message.
The above deprecation errors are coming from Embed → module.
-
- 🇮🇳India deepakkm
This is good to release, verified locally and its working fine.
- @chandu7929 opened merge request.
- First commit to issue fork.
- 🇮🇳India deepakkm
@japerry i'm not sure if you are referring to update the user_roles but even if we remove the method and change it with Role::loadMultiple() it wont break below drupal 10.2.
but i have still added version constraint to the code. Let me know if this looks good now. - @vishalkhode-0 opened merge request.
- 🇮🇳India vishalkhode
vishalkhode → made their first commit to this issue’s fork.
- 🇺🇸United States japerry KVUO
The code in the commit will break pre Drupal 10.2, and isn't required until Drupal 12. Should wait until gitlabci is building properly before this gets committed.
- @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.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-229708These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- 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.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-229708These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- @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.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-229708These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- 🇪🇸Spain rodrigoaguilera Barcelona
Fixed the small copy/paste mistakes.
It can be improved by using the deprecation helper but so far it looks good to me to release a D11 compatible version.
- First commit to issue fork.
- 🇳🇱Netherlands MegaChriz
Tests are passing on D11! I think this is ready for review and testing.
Note that phpstan (next major) is failing, but I think fixing that is out of scope for this issue.
- First commit to issue fork.