Support from Acquia helps fund testing for Drupal Acquia logo

Comments

robertoperuzzo created an issue. See original summary.

robertoperuzzo’s picture

robertoperuzzo’s picture

Assigned: robertoperuzzo » Unassigned
Status: Active » Needs review
MrPaulDriver’s picture

Tested okay with php 7.2 and 7.3

Tested with Drupal Check

adriancid’s picture

Title: Compatibility with Drupal 9 » Add the 'core_version_requirement' key in info.yml and composer.json files
Status: Needs review » Reviewed & tested by the community
FileSize
2.29 KB

We will commit this patch when D8.8 will be released.

adriancid’s picture

adriancid’s picture

oknate’s picture

oknate’s picture

Status: Reviewed & tested by the community » Needs work
romainj’s picture

When applying the patch #8 I can no longer install the Admin Toolbar Tools module.

adriancid’s picture

@romainj the patch #8 will only works for Drupal >= 8.8

oknate’s picture

Issue summary: View changes
oknate’s picture

It looks like we should update our tests to start testing against Drupal 8.8 before this is committed.

We should let people know, if they want to run less than Drupal 8.8, they'll need to restore the 'core: 8.x' part of the info file.

mmjvb’s picture

Suggest to revert #8 just because it restricts usage of the new release to Drupal versions supporting core_version_requirement. My understanding is that was introduced in 8.7.8, with plans to backport.

Why would you want to restrict the new release to those versions of Drupal ?

Apart from the fact it changes the scope of the issue which should be reflected in the summary!

Berdir’s picture

Yes, not sure why this mixes ^8 and ^8.8, since before it required 8.6 and nothing else was changed it seems like it should be fine to consistently use ^8.7.7 || ^9 now in all .info.yml and composer.json files (not sure if nested composer.json files even work but it's there now, so should go with it).

Berdir’s picture

Issue tags: +Drupal 9 readiness, +Novice
Berdir’s picture

adriancid’s picture

Berdir’s picture

Status: Needs review » Reviewed & tested by the community

Looks fine to me, not sure why you don't use the identical string in composer.json and info.yml (^9 vs 9.0 and spaces) but this should work fine ;)

  • adriancid committed ee04bc6 on 8.x-2.x
    Issue #3094517 by adriancid, oknate, robertoperuzzo, Berdir, mmjvb: Add...
adriancid’s picture

Status: Reviewed & tested by the community » Fixed

Thanks @Berdir, I just copy and paste from somewhere with this format, I will put before commit the same format in both place.

mondrake’s picture

Hi there, any plan for a point release with this included? Currently 2.0 does not install under D9 dev.

adriancid’s picture

@mondrake no fot the moment, you can use the dev version.

mondrake’s picture

Alright, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Kristen Pol’s picture

There was a discussion about adding the zero at the end of the versions in the #d9readiness Slack channel during Drupal 9 porting weekend and the consensus was that it's best practice to leave off the unnecessary zero, e.g.

Instead of:

core_version_requirement: ^8.7.7 || ^9.0

you are encouraged to use:

core_version_requirement: ^8.7.7 || ^9

Similar to the change record examples:

https://www.drupal.org/node/3070687

I've reviewed about 50 projects so far and almost all didn't include the extra zero.