Allow downloading and installing contrib modules in the next version

Add "Enabling ignore version control with Drush" under Remaining tasks.

There are local development composer setups from mstrelan, Joachim and dpi that solve some of these issues

Thanks for sharing, perhaps those projects can be used as inspiration? I think this feature should be baked into Drupal core.

Adding Drupal's Lenient Composer Endpoint to Drupal core has already been suggested by @catch:

We could consider adding the composer lenient plugin to core, then it's available to everyone who installs core. It would still be opt-in for installing particular extensions, it doesn't take over everything, just the things you explicitly tell it to install (iirc).

https://www.drupal.org/project/drupal/issues/3267143#comment-15034935 📌 Add a composer plugin that supports 'composer require-lenient' to support major version transitions Active

... and @mglaman added shortly after:

It sounds like the core_version_requirement in the module should just be deprecated in favor of composer.json constraints, period.

https://www.drupal.org/project/drupal/issues/3267143#comment-15035165 📌 Add a composer plugin that supports 'composer require-lenient' to support major version transitions Active

Updating issue summary with site builder.

Adding a sketch on how it could look on the Development page.

I don't see how this can go into the new development settings system because installing a module permanently affects config. If you install a module with this set, export config, deploy to production, lots of things will break. Would think this needs to be in settings.php somewhere.

Thanks for the feedback @catch, I have updated the proposed resolution.

This looks like a duplicate of 🐛 Allow contrib extensions to be enabled when core branch is 11.x/main Needs work ?

You're right that there is some overlap, but this issue proposes:

This should override both composer.json as well as *.info.yml limitations.

I think the other issue only deals with Drupal core limitations?

> This should override both composer.json as well as *.info.yml limitations.

That's already fixed in https://github.com/joachim-n/drupal-core-development-project.

I am grateful you created that solution, but my suggestion is to do this directly in Drupal core.

You could argue that 🐛 Allow contrib extensions to be enabled when core branch is 11.x/main Needs work is already solved by https://www.drupal.org/project/backward_compatibility → .

But I think it's better to solve this challenge directly in Drupal core, so I personally prefer 🐛 Allow contrib extensions to be enabled when core branch is 11.x/main Needs work .

> I am grateful you created that solution, but my suggestion is to do this directly in Drupal core.

My long-term plan is to get that Composer project template into core. There are a number of issues to fix first though. You could probably grab the code that allows Composer to allow installation of 10.x packages on 11.x and turn it into a core patch, but I think the work to do with Composer and the work to do with the extension system are best kept as two separate issues, as they're totally different systems.

In the meantime, I strongly recommend that anyone doing dev work on core use that template.

That sounds fantastic @joachim, I have updated the Issue Summary, since it looks like both download and install might be taken care of in those two issues.

I had a closer look at 🐛 Allow contrib extensions to be enabled when core branch is 11.x/main Needs work , and it looks dev-version specific ... I want to allow any Drupal 10 module to be installed in Drupal 11, basically like what https://www.drupal.org/project/backward_compatibility → offers.