- Issue created by @project update bot
- last update
about 1 year ago 12 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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- last update
about 1 year ago 12 pass - First commit to issue fork.
- last update
11 months ago 9 pass, 3 fail - last update
11 months ago 9 pass, 3 fail - π¦πΊAustralia darvanen Sydney, Australia
In MR13 I have:
- Dropped Drupal 9 support for the module and the testing submodule
- Added Drupal 11 support for the module and the testing submodule
- Turned on testing for 'next major'
No errors on the 'next major' tests that don't already exist on 'next minor'. I reckon that's good enough to commit, we have follow-ups for the errors.
- π¦πΊAustralia darvanen Sydney, Australia
Have manually tested an example form in Drupal 11 and it seems ok to me including the row-dragging behaviour which is where the only test failure is. Still trying to track down the reason for the test failure but that can happen in π PHPUnit failure with Drupal 10.3 Active if this gets committed.
45:19 53:42 Running- π¦πΊAustralia darvanen Sydney, Australia
PHPUnit tests are passing now, found the culprit.
- last update
10 months ago 12 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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
10 months ago 12 pass - last update
10 months ago 12 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
10 months ago 12 pass - Open on Drupal.org βCore: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
23:37 23:37 Queueing 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
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
23:24 23:24 Queueing The last submitted patch, 11: multivalue_form_element.1.0.x-dev.rector.patch, failed testing. View results β
- Status changed to Needs review
9 months ago 2:24am 24 June 2024 - π¦πΊAustralia darvanen Sydney, Australia
Please ignore the bot's patches, see the MR which is passing tests.
- Status changed to RTBC
3 months ago 4:09pm 24 December 2024 - πΊπΈUnited States weekbeforenext Asheville, NC
If anyone needs a patch for 1.0,0-beta6, you can use this one. The other patches don't apply to that version because of the d.o packaging info added to the multivalue_form_element.info.yml file.
- First commit to issue fork.
- π¦πΊAustralia darvanen Sydney, Australia
Additional commits look good to me and the proof is in the green tests. However standard review procedures prevent me from marking this RTBC. Thanks for the update @keszthelyi.
- π΅π±Poland gpietrzak WrocΕaw
Reviewed the code and tested, looks ok
-
joevagyok β
committed 9466f5ab on 1.0.x authored by
darvanen β
Issue #3433537: Drupal 11 compatibility.
-
joevagyok β
committed 9466f5ab on 1.0.x authored by
darvanen β
- Status changed to Fixed
about 1 month ago 10:24am 3 March 2025 Automatically closed - issue fixed for 2 weeks with no activity.