- 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.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-392907These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.2
- palantirnet/drupal-rector: 0.20.3
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-466239These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.5
- palantirnet/drupal-rector: 0.20.3
- First commit to issue fork.
- First commit to issue fork.
- 🇦🇺Australia elimw
Thanks @chrisfromredfin, I've tested the changes and they work for me.
-
elimw →
committed d182c38f on 3.0.x authored by
project update bot →
Issue #3499025 by elimw, chrisfromredfin: Automated Drupal 11...
-
elimw →
committed d182c38f on 3.0.x authored by
project update bot →
- heddn Nicaragua
Are there still issues after mering MR5 or should this be marked fixed?
- 🇺🇸United States chrisfromredfin Portland, Maine
If it stays open the bot can keep suggesting things as needed, but I suppose this is probably all that would be needed since 11.x API is stable.
- heddn Nicaragua
https://git.drupalcode.org/project/browsersync/-/pipelines => tests are not running, so at the least maybe we should fix that?
- 🇦🇺Australia elimw
@heddn, there's no pipelines currently configured for this project.
My plan is to do that as part of https://www.drupal.org/project/browsersync/issues/3523729 📌 Support object oriented hook implementations Active .
- First commit to issue fork.
- 🇦🇺Australia elimw
@jeremy1606, could you please make the relevant changes to https://www.drupal.org/project/browsersync/issues/3523729 📌 Support object oriented hook implementations Active instead? I'm going to close and hide your merge request as this issue is only for D11 compatibility fixes.
- heddn Nicaragua
Once 📌 Support object oriented hook implementations Active lands, then it should be a simple thing to just make the .info.yml changes.