- Issue created by @Harshita mehra
- Status changed to RTBC
over 1 year ago 1:02pm 19 June 2023 - 🇮🇳India Harshita mehra
Hello Maintainers,
I have provided a patch for this issue.
Please review.Thanks!
-
Arkener →
committed 182286f6 on 8.x-1.x authored by
Harshita mehna →
Issue #3367672 by Harshita mehna: The core: 8.x key must not be used...
-
Arkener →
committed 182286f6 on 8.x-1.x authored by
Harshita mehna →
- Status changed to Fixed
over 1 year ago 1:59pm 19 June 2023 - 🇳🇱Netherlands arkener
Good catch, thanks for the patch. This has now been fixed in the 1.x branch.
Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
over 1 year ago 11:31am 20 July 2023 - 🇮🇹Italy apaderno Brescia, 🇮🇹
Modules, themes. and profiles are allowed to use the following lines in their .info.yml file.
core: 8.x core_version_requirement: ^8 || ^9
That is described in New 'core_version_requirement' key in info.yml files for modules, themes and profiles → allows Composer semantic version constraints including specifying multiple major versions of core, which states:
For example a module that is compatible with Drupal 8 and Drupal 9 can have a info.yml file like this
name: My Module type: module core: 8.x core_version_requirement: ^8 || ^9