Support Migrate Plus >=4.2 and Drupal 10

Attaching a copy of MR !6 as of 014103e5 as Gitlab MR URLs are subject to unexpected changes (ref #3204538).

Patch applies cleanly, but the composer.lock does not update and then when you try to update the migration suites, it does not allow. So if you want to use this before the next release, you will have to do the following:

1. `composer remove drupal/media_migration`
2. Update the repositories section of your composer.json to the following:

"repositories": [
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8",
            "exclude": [
                "drupal/media_migration"
            ]
        },
        {
            "type": "git",
            "url": "git@git.drupal.org:issue/media_migration-3269743.git"
        }
]

3. `composer require drupal/media_migration:dev-3269743-support-drupal-10`
4. `composer require drupal/migrate_plus drupal/migrate_tools drupal/migrate_upgrade -W`

make sure you remove the patch..

@see https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa...

Thank you all!

I'm postponing this on #3263827: Make Migrate Magician compatible with Drupal core 10.x.
Right after it gets solved, I will merge this PR.

Pinging here since it looks like the issue in comment 6 was solved and part of a new Migrate Magician release.

This isn't postponed anymore.

Any word on getting a commit done on this?

Back to needs review with the proposed change.

I've tested the change and, while the patch applies cleanly and everything seems to work, I couldn't do the actual upgrade as Composer still sees the previous version constrain in the composer.lock file.

I added the patch to composer.json (using cweagans/composer-patches), then removed and required the project again with no luck (probably because of some caching?).

Anyway, I had to delete the lock file and run composer install for Composer to be able to finally see the changes and upgrade to Migrate Plus 6.0

Test dependencies also should be Drupal 10 compatible.

Test dependencies also should be Drupal 10 compatible.

Then please refocus this on compatibility with Migrate Plus 6 rather than blocking D9 sites from upgrading Migrate Plus and Migrate Tools.

Given #3297617 exists for actual Drupal 10 compatibility, let's focus this on just Migrate Plus 6 support.

Updated migrate_tools too.

Could we get some movement on this? I am unable to install this module with the patch method, and I cannot use the composer repository method as the issue fork is quite a bit behind dev.

Based the latest test run , it looks to me that migrate_upgrade constraint should be updated as well.

At the moment Drupal CI doesn't allow us to test changes to composer.json . From https://www.drupal.org/docs/creating-custom-modules/add-a-composerjson-f...

Tests of merge requests on the module will fail without a composer.json file, as will tests of patches that change the dependencies.

So I'm bumping priority in this regard - these changes should be merged ASAP. There is no big changes that could break client websites, also we are still in alpha here , so that is kinda allowed ;) .

For what it's worth, I rebased the issue branch off 8.x-1.x-dev so it has the latest code. This allows me to use the composer repo method.

I am not sure how to test this? Can we get composer instructions or can we go ahead and merge?

The merge request needs work to follow what's on the latest patch.

@DamienMcKenna the pull request has been updated with the updates in the latest patch.

@drupalninja99 if you would like to test the work in the feature branch, you can follow the instructions in #5

What else needs to be done to get this work into a new release?