dependabot-script icon indicating copy to clipboard operation
dependabot-script copied to clipboard

Unsatisfyable composer dependency breaks GitlabCI run

Open wilfriedwolf opened this issue 2 years ago • 0 comments

Hi there,

just experimenting with dependabot which I find a great tool.

Using a Magento 2.4.2-p2 I notice that the scheduled task will not succeed:

Having

    "require-dev": {
[...]
        "phpunit/phpunit": "^9",
        "sebastian/phpcpd": "~5.0.0",
[...]
    },

as a composer requirement. so sebastian/phpcpd exists in Version 6.0.3.Which can not be used with current phpunit/phpunit. Which is ok. But instead of skipping this trial the Gitlab-CI Script stops and fails. Which is bad, since the other dependencies will not be checked:

- Updating sebastian/phpcpd (from 5.0.2)…/home/dependabot/.bundle/gems/dependabot-composer-0.142.0/lib/dependabot/composer/file_updater/lockfile_updater.rb:224:in `handle_composer_errors': Your requirements could not be resolved to an installable set of packages. (Dependabot::DependencyFileNotResolvable)
  Problem 1
    - phpunit/phpunit is locked to version 9.1.5 and an update of this package was not requested.
    - sebastian/phpcpd 6.0.3 requires phpunit/php-timer ^5.0 -> satisfiable by phpunit/php-timer[5.0.0, 5.0.1, 5.0.2, 5.0.3].
    - You can only install one version of a package, so only one of these can be installed: phpunit/php-timer[3.1.4, 5.0.0, 5.0.1, 5.0.2, 5.0.3].
    - phpunit/phpunit 9.1.5 requires phpunit/php-timer ^3.1.4 -> satisfiable by phpunit/php-timer[3.1.4].

Is it possible to just catch such exceptions? Or define packges to skip?

Best Regards and Thanks in advance,

Willi

PS: I am using latest docker image.

wilfriedwolf avatar Apr 14 '22 12:04 wilfriedwolf