Skip to main content
Drupal Answers

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • What's the nature of the composer conflict? Is it due to the contrib module's composer.json? Commented Sep 17, 2020 at 17:46
  • An un-updated v8 contrib module from the official drupal repo will always require drupal/core:^8.something. The project is set up with drupal/core:^9.0.6 Commented Sep 17, 2020 at 17:49
  • 3
    I haven't jumped into D9 yet so not yet familiar with how the reqs work, but the reason I ask is that if the issue is due to the contrib module's composer.json then there is no way to handle the issue with a patch. See github.com/cweagans/…. Commented Sep 17, 2020 at 17:52
  • What @Mrweiner said - I spent a few hours trying to get around it some weeks back, without success Commented Sep 17, 2020 at 18:36
  • 1
    That's what I found too @Hudri - it's the core_version_requirement in the module's .info.yml which informs the packager of the core dependency. If that's not available, it's presumed to be just 8 (or it's derived from the core key instead perhaps) Commented Sep 17, 2020 at 19:09