D10 Readiness

+1 RTBC. The patch applies cleanly and adding the required Drupal 10 compatability.

+1. Kindly requesting a tagged release :-)

volodymyr.umanets → made their first commit to this issue’s fork.

volodymyr.umanets → closed merge request !2

I will add support for making a D10 release -- we are doing our upgrade and it appears folks have tested this above in the thread.

I am waiting for this also. We have a 10.x website using this patch and works fine.
Thanks.

Hope for a release soon! Thanks

Patch #2 is working for us but is complicated to use without a D10 compatible release being available.

@aczietlow, @andrewmacpherson, @Derimagia any chance this could get a committed and a new release tagged? Are you seeking new co-maintainers?

@joegraduate Using composer-drupal-lenient makes it easy patch in D10.

That composer plugin solved it for me as well.

Thanks for providing and reviewing the patch.

I created a release 8.x-2.0 that is D10 compatible.

For D10, doesn't core: 8.x need removed?

The 'core_version_requirement' constraint (^9.5 || ^10) requires the 'core' key not be set in modules/composer/migrate_devel/migrate_devel.info.yml

Yes. In order to be compatible with D10, you must remove core: 8.x.

Thanks!

I removed this and created a new release.

How can I see this error?

I got the error above when I ran a drush updb after I updated via composer.

The correct key was not removed in the last release.

Added a patch that removes the core: 8.x.

@nmangold patch didn't apply for me, patches on info.yml can be tricky - typically need some extra line returns in there.

@jackfoust. I think the problem here is this feature branch is not updated, and does not contain the latest changes from the 8.x-2.x branch. Specifically, the core version requirement was changed to ^9.5 in https://git.drupalcode.org/project/migrate_devel/-/commit/725b66750e1e69....

Here is another patch that will apply cleanly to THIS branch, before it is updated.

If I had push access to the issue branch, I could have updated the branch myself.

I probably made a mistake with the new release.

As far as I can see the line has now been removed from the info yml file in release 8.x-2.1

I tested this locally with composer.

Can you confirm this?

@nmangold let me know if you like to help maintaining the module.

@batigolix Your last commit fixed the issue. https://git.drupalcode.org/project/migrate_devel/-/commit/4bf1ecc56d1a07...

It looks like you did that at the same time I was creating this patch. I missed your comment.

I think this can be marked as fixed.

I updated this branch from 2.x, and pushed. So, this branch has the change, and everything is clear.

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