Automated Drupal 11 compatibility fixes for jsonapi_extras

Created on 3 March 2024, about 1 year ago
Updated 1 June 2024, 10 months ago

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 → .

📌 Task
Status

Closed: outdated

Version

3.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Pipeline finished with Success
    over 1 year ago
    #57386
  • Pipeline finished with Success
    over 1 year ago
    #58079
  • Pipeline finished with Success
    over 1 year ago
    Total: 266s
    #58120
  • Pipeline finished with Success
    over 1 year ago
    #58127
  • Pipeline finished with Canceled
    over 1 year ago
    #58295
  • Pipeline finished with Success
    over 1 year ago
    Total: 259s
    #58296
  • Pipeline finished with Success
    over 1 year ago
    Total: 181s
    #58336
  • Pipeline finished with Failed
    about 1 year ago
    Total: 326s
    #79471
  • Pipeline finished with Failed
    about 1 year ago
    Total: 192s
    #108192
  • Pipeline finished with Failed
    about 1 year ago
    #108196
  • Issue created by @project update bot
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • Pipeline finished with Failed
    about 1 year ago
    Total: 208s
    #109738
  • 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.

  • First commit to issue fork.
  • Assigned to PrabuEla
  • 🇮🇳India PrabuEla chennai
  • 🇮🇳India PrabuEla chennai
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 🇮🇳India PrabuEla chennai

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

  • Pipeline finished with Failed
    about 1 year ago
    Total: 204s
    #110424
  • Issue was unassigned.
  • 🇮🇳India PrabuEla chennai
  • Status changed to Needs review about 1 year ago
  • 🇮🇳India PrabuEla chennai
  • Pipeline finished with Failed
    about 1 year ago
    Total: 728s
    #111629
  • Pipeline finished with Success
    about 1 year ago
    Total: 159s
    #112936
  • Pipeline finished with Success
    about 1 year ago
    Total: 156s
    #112941
  • Pipeline finished with Success
    about 1 year ago
    Total: 158s
    #112947
  • Pipeline finished with Success
    about 1 year ago
    Total: 163s
    #112955
  • Pipeline finished with Success
    about 1 year ago
    Total: 159s
    #112965
  • Pipeline finished with Success
    about 1 year ago
    Total: 155s
    #112978
  • Pipeline finished with Failed
    about 1 year ago
    #113540
  • 🇳🇱Netherlands bbrala Netherlands
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 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.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 🇳🇱Netherlands bbrala Netherlands
  • Status changed to Needs work about 1 year ago
  • 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.

  • Status changed to Needs review about 1 year ago
  • 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
  • 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
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 🇳🇱Netherlands bbrala Netherlands
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • Pipeline finished with Failed
    about 1 year ago
    Total: 299s
    #114428
  • 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.

  • Pipeline finished with Failed
    about 1 year ago
    Total: 409s
    #116981
  • Pipeline finished with Failed
    about 1 year ago
    Total: 379s
    #117000
  • Pipeline finished with Failed
    about 1 year ago
    Total: 280s
    #117157
  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • Pipeline finished with Failed
    about 1 year ago
    Total: 208s
    #120033
  • 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.

  • Pipeline finished with Success
    about 1 year ago
    Total: 147s
    #121135
  • Pipeline finished with Skipped
    about 1 year ago
    #123621
  • Pipeline finished with Failed
    about 1 year ago
    Total: 149s
    #125674
  • Pipeline finished with Success
    about 1 year ago
    Total: 185s
    #125680
  • Pipeline finished with Success
    about 1 year ago
    Total: 148s
    #126986
  • Pipeline finished with Success
    about 1 year ago
    Total: 229s
    #127732
  • Pipeline finished with Skipped
    about 1 year ago
    #128994
  • Pipeline finished with Success
    about 1 year ago
    Total: 172s
    #130115
  • Pipeline finished with Failed
    about 1 year ago
    Total: 196s
    #131958
  • Pipeline finished with Failed
    about 1 year ago
    #131963
  • Pipeline finished with Failed
    about 1 year ago
    Total: 136s
    #131977
  • Pipeline finished with Success
    about 1 year ago
    Total: 215s
    #132003
  • 🇳🇱Netherlands bbrala Netherlands
  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 🇳🇱Netherlands bbrala Netherlands
  • 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.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 🇳🇱Netherlands bbrala Netherlands
  • 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.

  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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 changed to Needs review about 1 year ago
  • 🇳🇱Netherlands bbrala Netherlands
  • 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.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 🇳🇱Netherlands bbrala Netherlands
  • 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.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • 🇳🇱Netherlands bbrala Netherlands
  • 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.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • Pipeline finished with Failed
    about 1 year ago
    Total: 237s
    #136390
  • 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.

  • 🇳🇱Netherlands bbrala Netherlands

    check for logic around missing post rector file.

  • Status changed to Needs review about 1 year ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • 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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update about 1 year ago
    11 pass, 4 fail
  • Pipeline finished with Failed
    about 1 year ago
    Total: 253s
    #137166
  • 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.

  • Pipeline finished with Success
    12 months ago
    #141450
  • Pipeline finished with Success
    12 months ago
    Total: 239s
    #143274
  • Pipeline finished with Success
    12 months ago
    Total: 614s
    #146743
  • Pipeline finished with Success
    11 months ago
    Total: 286s
    #158735
  • Pipeline finished with Success
    11 months ago
    Total: 305s
    #176411
  • Pipeline finished with Success
    11 months ago
    Total: 411s
    #176945
  • Status changed to Needs review 10 months ago
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 10 months ago
    20 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.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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 10 months ago
    20 pass
  • Pipeline finished with Success
    10 months ago
    Total: 209s
    #183198
  • 🇬🇧United Kingdom jonathan1055

    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.

  • Status changed to Closed: outdated 10 months ago
  • 🇳🇱Netherlands bbrala Netherlands

    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.

  • 🇬🇧United Kingdom jonathan1055

    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

  • Pipeline finished with Skipped
    10 months ago
    #193895
  • Pipeline finished with Success
    10 months ago
    #198878
  • Pipeline finished with Success
    10 months ago
    Total: 132s
    #198879
  • Pipeline finished with Success
    10 months ago
    Total: 445s
    #204761
  • Pipeline finished with Success
    9 months ago
    Total: 1374s
    #209296
  • Pipeline finished with Success
    9 months ago
    Total: 257s
    #211290
  • Pipeline finished with Success
    9 months ago
    Total: 164s
    #226403
  • Pipeline finished with Skipped
    9 months ago
    #231792
  • Pipeline finished with Success
    8 months ago
    Total: 79s
    #236278
  • Pipeline finished with Success
    8 months ago
    Total: 165s
    #260671
  • Pipeline finished with Success
    8 months ago
    Total: 308s
    #261962
  • Pipeline finished with Success
    7 months ago
    Total: 301s
    #262782
  • Pipeline finished with Success
    7 months ago
    Total: 311s
    #264512
  • Pipeline finished with Success
    7 months ago
    Total: 260s
    #265595
  • Pipeline finished with Success
    7 months ago
    Total: 144s
    #265607
  • Pipeline finished with Failed
    7 months ago
    Total: 154s
    #270142
  • Pipeline finished with Failed
    7 months ago
    Total: 181s
    #271169
  • Pipeline finished with Success
    7 months ago
    Total: 144s
    #277770
  • Pipeline finished with Success
    7 months ago
    Total: 218s
    #288167
  • Pipeline finished with Success
    6 months ago
    Total: 221s
    #289887
  • Pipeline finished with Skipped
    6 months ago
    #291108
  • Pipeline finished with Failed
    6 months ago
    Total: 193s
    #292544
  • Pipeline finished with Success
    6 months ago
    Total: 219s
    #292739
  • Pipeline finished with Failed
    6 months ago
    Total: 397s
    #292797
  • Pipeline finished with Canceled
    6 months ago
    #293281
  • Pipeline finished with Success
    6 months ago
    Total: 4227s
    #293287
  • Pipeline finished with Success
    6 months ago
    #293367
  • Pipeline finished with Failed
    6 months ago
    #302893
  • Pipeline finished with Failed
    6 months ago
    #302910
  • Pipeline finished with Failed
    6 months ago
    #302917
  • Pipeline finished with Failed
    6 months ago
    #302936
  • Pipeline finished with Success
    6 months ago
    #302980
  • Pipeline finished with Success
    6 months ago
    #303000
  • Pipeline finished with Success
    6 months ago
    #303009
  • Pipeline finished with Success
    6 months ago
    #303121
  • Pipeline finished with Success
    6 months ago
    #303132
  • Pipeline finished with Canceled
    6 months ago
    Total: 194s
    #303357
  • Pipeline finished with Success
    6 months ago
    Total: 236s
    #303361
  • Pipeline finished with Failed
    5 months ago
    Total: 151s
    #317164
  • Pipeline finished with Skipped
    5 months ago
    #324951
  • Pipeline finished with Success
    5 months ago
    Total: 253s
    #330070
  • Pipeline finished with Success
    5 months ago
    Total: 224s
    #330084
  • Pipeline finished with Success
    5 months ago
    Total: 221s
    #330339
  • Pipeline finished with Failed
    5 months ago
    Total: 163s
    #330812
  • Pipeline finished with Failed
    5 months ago
    Total: 243s
    #341089
  • Pipeline finished with Success
    5 months ago
    Total: 215s
    #341255
  • Pipeline finished with Success
    4 months ago
    Total: 210s
    #349925
  • Pipeline finished with Failed
    3 months ago
    Total: 330s
    #390060
  • Pipeline finished with Success
    3 months ago
    Total: 231s
    #390070
  • Pipeline finished with Success
    3 months ago
    Total: 143s
    #391104
  • Pipeline finished with Success
    3 months ago
    Total: 164s
    #391866
  • Pipeline finished with Success
    2 months ago
    Total: 213s
    #401773
  • Pipeline finished with Success
    2 months ago
    Total: 185s
    #405495
  • Pipeline finished with Success
    about 1 month ago
    Total: 339s
    #441317
  • Pipeline finished with Success
    30 days ago
    Total: 170s
    #441972
  • Pipeline finished with Success
    30 days ago
    Total: 172s
    #441975
  • Pipeline finished with Failed
    15 days ago
    Total: 131s
    #453845
  • Pipeline finished with Failed
    12 days ago
    Total: 486s
    #456390
  • Pipeline finished with Success
    5 days ago
    Total: 143s
    #461441
  • Pipeline finished with Success
    about 12 hours ago
    #465924
Production build 0.71.5 2024