-
-
Notifications
You must be signed in to change notification settings - Fork 111
Closed
Labels
Description
Hi @Ocramius I just ran into an interesting conflict on which I wouldn't mind a second pair of eyes/some advise.
I'm setting up some PRs to switch various PHPCS external standards to the new fork for PHPCS. As these are external standards, they use dev-master
in certain places in CI.
Now this is a conflict I ran into for one of these:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires phpcsstandards/php_codesniffer dev-master -> satisfiable by phpcsstandards/php_codesniffer[dev-master].
- roave/security-advisories dev-master conflicts with squizlabs/php_codesniffer >=1,<2.8.1|>=3,<3.0.1 (phpcsstandards/php_codesniffer dev-master replaces squizlabs/php_codesniffer > 2.0).
- Root composer.json requires roave/security-advisories dev-master -> satisfiable by roave/security-advisories[dev-master].
Commit: PHPCSStandards/PHPCSDevTools@5e78785
Workflow script: https://github.com/PHPCSStandards/PHPCSDevTools/blob/feature/switch-to-fork-of-phpcs/.github/workflows/cs.yml
Build log: https://github.com/PHPCSStandards/PHPCSDevTools/actions/runs/7064957528/job/19233994486
It goes without saying that using dev-master
for the original squizlabs
package did not run into this issue.
Any suggestions//advise ?