Fix default_content dependency

Here is a patch that solves this problem. It still couples this alpha release to the alpha release of default_content, but it's no longer a specific, now outdated, release.

Unfortunately, I wasn't able to apply it using the cweagans/composer-patches. This may be the case because it's not patching code, but the composer.json file, which almost creates a race condition...

Perhaps now that this patch file is not local, but rather external, the extra/patches mechanism might pick it up and "fix everything".

I marked this as major because, unless I'm wrong, which I often am, there is no reason to couple this release of default_content_deploy with default_content release alpha7. Minor versions should be non-breaking, so it should not matter which alpha release is used. (This could be a bit of wishful thinking, but a guy can hope!)

Please commit this to dev

Hey, any chance to get that committed?

any news on this?

Thank you guys and very sorry for the late reaction.

Hi,

I just tried composer require 'drupal/default_content_deploy:1.x-dev'

But I get this one

The requested package drupal/default_content ^1.x-dev exists as drupal/default_content[dev-1.x, 1.x-dev, 1.0.0-alpha8, 1.0.0-alpha7, 1.0.0-alpha6, 1.0.0-alpha5, 1.0.0-alpha4, 1.0.0-alpha3, 1.0.0-alpha2, 1.0.0-alpha1, dev-8.x-1.x, dev-uuid-tree] but these are rejected by your constraint.

Thanks

PS: "minimum-stability": "dev"

I checked it again without any problem.
composer require 'drupal/default_content_deploy:1.x-dev' works normally for me.

Could it be a problem in typo? You asked for default_content_deploy, but your Composer message is:
> The requested package drupal/default_content ^1.x-dev exists as... So maybe you asked for default_content:1.x-dev.

Removing default_content and better_normalizers from composer.json and run composer require 'drupal/default_content_deploy:1.x-dev' fixed the issue for me.

Thanks