Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Per https://www.drupal.org/node/3070687, the new key needs to be used instead of core: 8.x (when requiring anything other than just ^8) to be able to actually install/test the module against D9.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | commerce-d9-3103948-2.patch | 15.53 KB | Berdir |
| |||
Comments
Comment #2
BerdirNote: test-runs against 9.0.x are only possible once this is committed (as the patch is only applied after initially requiring the module) and all dependencies have been updated accordingly.
It's also possible to remove the drupal:system dependency now as this serves the same purpose.
The trick with removing the core key is that core versions below 8.7.7 will fail with a parse exception on info.yml files without the core key.
Comment #3
BerdirFYI, cross-referencing dependency issues:
entity: #3086597: Add new key core_version_requirement in entity.info.yml
IEF: #3098018: Make Inline Entity Form D9 Ready
Address: #3103952: Add core_version_requirement to allow installation on D9
Comment #5
bojanz CreditAttribution: bojanz at Centarro commentedCommitted the Entity API and Address issues, as well as this issue. Thanks!
Opened issues for Profile (#3105064: Add core_version_requirement key) and State Machine (#3105065: Require Drupal 8.7.7, add core_version_requirement key).