- Issue created by @project update bot
- last update
9 months ago 86 pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , 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.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Merge request !47Issue #3430593: Make compatible with Drupal 11 → (Merged) created by project update bot
- last update
9 months ago 86 pass - last update
9 months ago 86 pass This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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.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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- last update
9 months ago 86 pass - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
Liam Morland → made their first commit to this issue’s fork.
- last update
9 months ago 86 pass - last update
9 months ago 86 pass - last update
9 months ago 86 pass - last update
9 months ago 86 pass -
Liam Morland →
committed 670b97c3 on 5.1.x authored by
Project Update Bot →
Issue #3430593: Make compatible with Drupal 11
-
Liam Morland →
committed 670b97c3 on 5.1.x authored by
Project Update Bot →
- Status changed to Active
9 months ago 7:13pm 5 April 2024 -
Liam Morland →
committed 739390a4 on 5.1.x
Issue #3430593: Remove use of deprecated GuzzleHttp\json_decode/...
-
Liam Morland →
committed 739390a4 on 5.1.x
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Status changed to Needs review
6 months ago 12:46am 18 June 2024 -
Liam Morland →
committed 71b854c8 on 5.1.x authored by
Project Update Bot →
Issue #3430593: Automated Project Update Bot fixes
-
Liam Morland →
committed 71b854c8 on 5.1.x authored by
Project Update Bot →
-
Liam Morland →
committed 09b079d8 on 5.1.x
Issue #3430593: Replace deprecated EntityReferenceTestTrait with...
-
Liam Morland →
committed 09b079d8 on 5.1.x
-
Liam Morland →
committed 1c637f69 on 5.1.x
Issue #3430593: Drop support for Drupal 10.1
-
Liam Morland →
committed 1c637f69 on 5.1.x
-
Liam Morland →
committed f225cb1f on 5.1.x
Issue #3430593: Remove obsolete default_argument_skip_url setting This...
-
Liam Morland →
committed f225cb1f on 5.1.x
- Status changed to Active
6 months ago 6:06pm 18 June 2024 - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
All changes above have been made except those that require Drupal 10.3. These deprecations will not be removed until Drupal 12.
Leaving open for more patches.
-
liam morland →
committed 4a2976a1 on 5.2.x
Issue #3430593: Update core_version_requirement in sub-modules
-
liam morland →
committed 4a2976a1 on 5.2.x
- Merge request !53Draft: Remove webform test to allow Drupal 11 testing → (Open) created by Liam Morland
-
liam morland →
committed 1bc2ca70 on 5.2.x
Issue #3430593: Update function signature in call to ConfigFormBase::...
-
liam morland →
committed 1bc2ca70 on 5.2.x