Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated changes until this issue is closed

    If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot, such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue. For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue.

CommentFileSizeAuthor
#46 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt6.61 KBproject update bot
#46 jsonapi_extras.3.x-dev.rector.patch7.39 KBproject update bot
#46 interdiff-last-bot.6921797.txt1.33 KBproject update bot
#44 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#44 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#44 interdiff-last-bot.6921515.txt0 bytesproject update bot
#41 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#41 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#38 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#38 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#35 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#35 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#32 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#32 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#29 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#29 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#26 jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KBproject update bot
#26 jsonapi_extras.3.x-dev.rector.patch8.85 KBproject update bot
#23 jsonapi_extras.8.x-3.24.rector.patch8.85 KBproject update bot
#23 interdiff-last-bot.6907399.txt4.53 KBproject update bot
#21 jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KBproject update bot
#21 jsonapi_extras.8.x-3.24.rector.patch2.78 KBproject update bot
#19 jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KBproject update bot
#18 jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KBproject update bot
#17 jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KBproject update bot
#14 a11y_form_helpers.2.0.1.upgrade_status.post_rector.txt0 bytesproject update bot
#14 jsonapi_extras.8.x-3.24.rector.patch2.78 KBproject update bot
#12 a11y_form_helpers.2.0.1.upgrade_status.post_rector.txt0 bytesproject update bot
#12 jsonapi_extras.8.x-3.24.rector.patch2.78 KBproject update bot
#2 jsonapi_extras.8.x-3.24.rector.patch2.78 KBproject update bot

Issue fork jsonapi_extras-3425243

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

project update bot commented
Status: Active » Needs review
StatusFileSize
new jsonapi_extras.8.x-3.24.rector.patch2.78 KB

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.19.2, 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-109123

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.2.7
  2. palantirnet/drupal-rector: 0.19.2

Project Update Bot opened merge request !44

Status: Needs review » Needs work

The last submitted patch, 2: jsonapi_extras.8.x-3.24.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

rishabjasrotia made their first commit to this issue’s fork.

prabuela’s picture

prabuela commented
Assigned: Unassigned » prabuela
Issue summary: View changes
prabuela’s picture

prabuela commented
prabuela’s picture

prabuela commented

Rebased the latest changes of 8.x-3.x

prabuela’s picture

prabuela commented
Assigned: prabuela » Unassigned
prabuela’s picture

prabuela commented
Status: Needs work » Needs review
bbrala’s picture

bbrala
Location Netherlands
commented
project update bot’s picture

project update bot commented
Issue summary: View changes
StatusFileSize
new jsonapi_extras.8.x-3.24.rector.patch2.78 KB
new a11y_form_helpers.2.0.1.upgrade_status.post_rector.txt0 bytes

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2

Status: Needs review » Needs work

The last submitted patch, 12: jsonapi_extras.8.x-3.24.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.8.x-3.24.rector.patch2.78 KB
new a11y_form_helpers.2.0.1.upgrade_status.post_rector.txt0 bytes

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 14: jsonapi_extras.8.x-3.24.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KB

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2
project update bot’s picture

project update bot commented
StatusFileSize
new jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KB

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2
project update bot’s picture

project update bot commented
StatusFileSize
new jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KB

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes
project update bot’s picture

project update bot commented
Issue summary: View changes
StatusFileSize
new jsonapi_extras.8.x-3.24.rector.patch2.78 KB
new jsonapi_extras.8.x-3.24.upgrade_status.post_rector.txt6.4 KB

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.19.2, 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.

Using the merge request

To work on the code of the merge request, please commit the changes to the issue branch. The project-update-bot-only branch WILL be overwritten by new changes from the bot.

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-109123

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.19.2

Status: Needs review » Needs work

The last submitted patch, 21: jsonapi_extras.8.x-3.24.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Status: Needs work » Needs review
StatusFileSize
new interdiff-last-bot.6907399.txt4.53 KB
new jsonapi_extras.8.x-3.24.rector.patch8.85 KB

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.0, 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-115424

This patch was created using these packages:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.7
  3. palantirnet/drupal-rector: 0.20.0

Status: Needs review » Needs work

The last submitted patch, 23: jsonapi_extras.8.x-3.24.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes
project update bot’s picture

project update bot commented
Version: 8.x-3.24 » 8.x-3.x-dev
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 26: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 29: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 32: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 35: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1
bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

Status: Needs review » Needs work

The last submitted patch, 38: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-134377

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.9
  3. palantirnet/drupal-rector: 0.20.1

Status: Needs review » Needs work

The last submitted patch, 41: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

bbrala’s picture

bbrala
Location Netherlands
commented
Issue summary: View changes

check for logic around missing post rector file.

project update bot’s picture

project update bot commented
Title: Automated Drupal 11 compatibility fixes » Automated Drupal 11 compatibility fixes for jsonapi_extras
Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new interdiff-last-bot.6921515.txt0 bytes
new jsonapi_extras.3.x-dev.rector.patch8.85 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt7.14 KB

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-136651

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.1.0
  2. mglaman/phpstan-drupal: 1.2.10
  3. palantirnet/drupal-rector: 0.20.1

Status: Needs review » Needs work

The last submitted patch, 44: jsonapi_extras.3.x-dev.rector.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

project update bot’s picture

project update bot commented
Status: Needs work » Needs review
StatusFileSize
new interdiff-last-bot.6921797.txt1.33 KB
new jsonapi_extras.3.x-dev.rector.patch7.39 KB
new jsonapi_extras.3.x-dev.upgrade_status.post_rector.txt6.61 KB

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-181965

These packages were used to generate the fixes:

  1. drupal/upgrade_status: 4.3.1
  2. mglaman/phpstan-drupal: 1.2.11
  3. palantirnet/drupal-rector: 0.20.1
jonathan1055’s picture

jonathan1055 commented
Issue summary: View changes

Hi bbrala,
Are you OK if I use this MR to test the changes in #3449621: Add rule for project-update-bot to test against next major ?
I will revert the test afterwards. Given that you opened that issue, this seems a good place to test the MR.

bbrala’s picture

bbrala
Location Netherlands
commented
Status: Needs review » Closed (outdated)
Issue tags: -ProjectUpdateBotD11, -Drupal 11 compatibility

Closing out this issue to get a fresh one, there has been some testing here. Will go through issues later to consolidate the actual help given.

jonathan1055’s picture

jonathan1055 commented

Yes, that's good. As you know, #3449621: Add rule for project-update-bot to test against next major was committed, but also the default-ref tag was moved to include this, so all contrib that are using the recommended gitlab_templates repo now have the automatic Next Major testing on the project-update-bot-only branch.
https://git.drupalcode.org/project/gitlab_templates/-/tags

Thank you for raising that issue, it is a good enhancement.