Timeline for Require v8 only contrib module with v9 patch
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2021 at 13:39 | answer | added | Joao Ventura | timeline score: 3 | |
| Feb 2, 2021 at 16:26 | answer | added | James Williams | timeline score: 7 | |
| Oct 6, 2020 at 15:48 | vote | accept | Hudri | ||
| Sep 22, 2020 at 23:00 | answer | added | Darvanen | timeline score: 18 | |
| Sep 18, 2020 at 6:00 | history | tweeted | twitter.com/StackDrupal/status/1306835349533061120 | ||
| Sep 17, 2020 at 19:09 | comment | added | Clive♦ | 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) | |
| Sep 17, 2020 at 18:59 | comment | added | Hudri | I don't think the issue is coming from the module's composer.json file - at least not directly. When I fork the module with git, there is no core dependency/version constraint in the module's composer file itself at all, only in the module.info.yml. There seems to be some Drupalism in the packagist server that translates a module.info.yml version constraint into a composer version constraint. | |
| Sep 17, 2020 at 18:46 | comment | added | Matthew Weiner | @Clive same here, lost several hours trying to get around it. Some things just can't be handled no matter how clever I think I am. | |
| Sep 17, 2020 at 18:36 | comment | added | Clive♦ | What @Mrweiner said - I spent a few hours trying to get around it some weeks back, without success | |
| Sep 17, 2020 at 17:52 | comment | added | Matthew Weiner | 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/…. | |
| Sep 17, 2020 at 17:49 | comment | added | Hudri | 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 | |
| Sep 17, 2020 at 17:46 | comment | added | Matthew Weiner | What's the nature of the composer conflict? Is it due to the contrib module's composer.json? | |
| Sep 17, 2020 at 16:58 | history | edited | Hudri | CC BY-SA 4.0 | added 1 character in body |
| Sep 17, 2020 at 16:10 | history | asked | Hudri | CC BY-SA 4.0 |