When I install the latest version of Deploy (using Composer, i.e. composer require 'drupal/deploy:^1.0') on Drupal 8.4, I get a permanent error message in my site's configuration screens (e.g. Reports -> Status Report, among other places):

The installed version of at least one of your modules or themes is no longer supported. Upgrading or disabling is strongly recommended. See the project homepage for more details. See the available updates page for more information and to install your missing updates.

Sometimes you have to run Extend->Update->Check Manually before the error appears.

It's being caused because Deploy has Multiversion as a dependency, which in turn has has Conflict 8.x-1.0 as a dependency. But clearly Drupal 8.x does not recognize Conflict 8.x-1.0 as a supported module...

I'm not exactly clear on how the updating/supported modules process is controlled, is this fixable in this project? Or in the Multiversion project (there's already a bug report here)? Do we need to get Conflict to put out a stable release for 8.x first?

In any event, I'd sure like to get rid of that error message...

Comments

cbanack created an issue. See original summary.

MattBrigade’s picture

I see that there's a 8.x-2.x-dev branch for Conflict. Have you tried to see if that works? Once I get Deploy up and working on my site I'll update Conflict to 2.x-dev and see what happens.

Manuel Garcia’s picture

Multiversion module currently has this on its composer.json:
"drupal/conflict": "^1-beta" https://cgit.drupalcode.org/multiversion/tree/composer.json#n8

But, there is no beta release on the 1.x branch yet. So at least that should be fixed in my opinion. I don't think thats enough to cause the error mentioned on the description though...

vijaycs85’s picture

Status: Active » Postponed (maintainer needs more info)

Looks like some data here are outdated:

1.

It's being caused because Deploy has Multiversion as a dependency

Don't see multiversion as a dependency anymore.

2.

But, there is no beta release on the 1.x branch yet.

- There is a stable 1.0 release now.

Could we try again and see if this is still an issue?