requires downstream users to declare our forked vipwpcs in repositories to avoid install failure #5
Description
This should be handled entirely in this project so that downstream does not need to jump through hoops.
Problem 1
- Root composer.json requires kleinweb/php-coding-standards ^0.4.0 -> satisfiable by kleinweb/php-coding-standards[0.4.0].
- kleinweb/php-coding-standards 0.4.0 requires automattic/vipwpcs dev-wpcs-develop -> found automattic/vipwpcs[dev-rebecca/old_font_sniff, dev-rebecca/fix_unit_tests, dev-fix/wpcs-compatibility, dev-feature/restrict-filemtime, dev-options_race_sniff, dev-custom_keywords_includingfile, dev-remove_redundant_outputnotscapedsniff, dev-feature/custom-report, dev-rebecca/fix_113, dev-rebecca/fix_407, dev-wpcs-dev-compatible, dev-rebecca/add_restrictedcachegroups, dev-rebecca/adjust_lowcacheexpirysniff, dev-master, dev-release/2.3.4, dev-develop, 0.2.1, ..., 0.4.0, 1.0.0, 2.0.0, ..., 2.3.3] but these do not match your constraint and are therefore not installable. Make sure you either fix the constraint or avoid updating this package to keep the one present in the lock file (automattic/vipwpcs[dev-wpcs-develop]).
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.