Make dmu-upgrade itself run without errors on Drupal 10

@jcnventura: There is https://github.com/drupal but it does not seem to have non-core packages. You can move it to my namespace for now I guess. We can update the module to pull it from there. Also I attempted to accept the invite, but it expired, sorry. Can you invite me again?

Setting priority to Major, as Drupal 9 EOL is close.

The Pharborist that we will use is now at https://github.com/pharborist/pharborist. I retitled 📌 Make the code generated Drupal 10 compatible Active to make it clearer how different is that one, and retitling this one too. So this is about making the module run on Drupal 10 while 📌 Make the code generated Drupal 10 compatible Active is about the resulting code being Drupal 10 compatible. We need this one done first, otherwise it does not make much sense.

Since this would be officially dropping Drupal 8 support, could/should we tie this to a new major version? If so, we could open a 2.x branch and commit this change, allowing the module to be installed on D10 with a dev release. This might make working on 📌 Make the code generated Drupal 10 compatible Active a bit easier.

@markdorison, there's no need to create a new branch

all that has to be done is to have the correct constraints set to the composer.json

example
^9.5 || ^10 || ^11

then anyone with D8 will be getting the previous release that mentions ^8

better than that, I think there's a pattern available for
>=10 this would not limit to 10

This is probably still needed, there are still many important D6/D7 only projects that would still be very useful for D10/D11 and beyond

@joseph.olstad I fully agree! Any active maintainers left here? It's sad to see this abandoned. :(

This needs a lot of work, and not simply adding "^10 || ^11".

First of all, it seems that it doesn't work in PHP 8. That basically means that it doesn't even run in Drupal 10. We need 🐛 dmu_upgrade not compatible with PHP 8.0+ Needs review to be RTBC and merged. We also need 📌 Make the code generated Drupal 10 compatible Active to be fixed.

I don't use this module anymore, as I don't have any D7 custom code. @gábor hojtsy was very interested in this at one time. Not sure if Acquia uses anything from this module in https://www.drupal.org/project/acquia_migrate → . If any of you is interested in maintaining this, please do fix the above issues, and I'll grant you co-admin rights to tag new releases.

Also, interesting bit, @joseph.olstad is one of the co-maintainers..