Automated Drupal 10 compatibility fixes

Are there any updates on when this issue will be resolved?

I've applied the automatically generated patch on my local and verified that the "NULL" filter field is a select able sort filter and their order options "Sort NULL last" / Sort NULL first" works. However i am using this module the first time and not aware if there any config variations that should get tested manually.

I´m not sure why, but for me the patch couldn´t apply to the info.yml when installed with composer.
In case anyone stumbles accross the same i share the patch i used

It's impossible to apply a compatibility patch with composer because the patch is applied after installing the package. I've created a MR so it should be possible if you follow the instructions written here → .

To whomever ends up committing this - please commit it to the 8.x-1.x branch, please don't continue work on the 1.x, 9.1.x or 9.x-1.x branches.

another option to apply this patch is to use https://chromatichq.com/insights/patching-info-files-composer/ with the composer-drupal-lenient package:

https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →

Awesome @munchmunch,

Yall will have a new release come this Friday. I'll take Damien's comment under advisement too.

@DamienMcKenna,

I got most of that branching cleaned up... 9.1.x is tied to a dev release which is unfortunate.

Everyone else,
Testing the fixes here now and If all is well I'll create a release.

Rejoice 8.x-1.2 has been released.

Just curious, should this issue remain open for ProjectUpdateBotD10 to continue working if more rector fixes come available, or should we assume there won't be any more?

I don't think there's any point to the bot running again, so it might as well be left closed.

Automatically closed - issue fixed for 2 weeks with no activity.