- Issue created by @project update bot
- last update
10 months ago 23 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 β 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, 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
- last update
10 months ago 23 pass - last update
8 months ago 23 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 β 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-188815These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- last update
8 months ago 23 pass - last update
7 months ago 18 pass, 1 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 β 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-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
- last update
7 months ago 18 pass, 1 fail The last submitted patch, 5: fraction.2.x-dev.rector.patch, failed testing. View results β
- πΊπΈUnited States m.stenta
m.stenta β made their first commit to this issueβs fork.
- πΊπΈUnited States m.stenta
- Rebased this on top of π Enable GitLab CI intergration Active so we can run tests.
- Re-enabled running of tests against the current version of Drupal (11) (in addition to previous version).
- Test against the maximum available version of PHP (per comment here: https://www.drupal.org/project/fraction/issues/3498271#comment-15933501 π Enable GitLab CI intergration Active ).
- Updated PostgreSQL to 16 in tests.
- Discovered an issue with the way the fraction field type category was declared, which doesn't break anything in Drupal 10, but causes a 500 white screen in Drupal 11, so I fixed that and tagged a new 2.3.2 release: https://www.drupal.org/project/fraction/issues/3430694 π Automated Drupal 11 compatibility fixes for fraction Needs work
- Started a new 3.x branch, which will support Drupal 11, and remove support for Drupal 9.
Tests are green, and manual testing works as expected. I think this is good to merge! I'll tag a new 3.0.0 release afterwards.
-
m.stenta β
committed 31612bd7 on 3.x
Issue #3430694: Drupal 11 support
-
m.stenta β
committed 31612bd7 on 3.x
Automatically closed - issue fixed for 2 weeks with no activity.