Closed szepeviktor closed 4 years ago
There is a release blocking problem.
"wp-cli/cache-command": "^2", "wp-cli/checksum-command": "^2", "wp-cli/config-command": "^2", "wp-cli/core-command": "^2", "wp-cli/cron-command": "^2", "wp-cli/db-command": "^2", "wp-cli/embed-command": "^2", "wp-cli/entity-command": "^2", "wp-cli/eval-command": "^2", "wp-cli/export-command": "^2", "wp-cli/extension-command": "^2", "wp-cli/i18n-command": "^2", "wp-cli/import-command": "^2", "wp-cli/language-command": "^2", "wp-cli/media-command": "^2", "wp-cli/package-command": "^2", "wp-cli/rewrite-command": "^2", "wp-cli/role-command": "^2", "wp-cli/scaffold-command": "^2", "wp-cli/search-replace-command": "^2", "wp-cli/server-command": "^2", "wp-cli/shell-command": "^2", "wp-cli/super-admin-command": "^2", "wp-cli/widget-command": "^2", "wp-cli/wp-cli": "^2.1.0"
wp-cli/wp-cli-bundle has these loose constrains: thus we are unable to automatically reconstruct the packages versions at release v2.1.0 etc.
wp-cli/wp-cli-bundle
What to do know??
It is easy to fix wp-cli/wp-cli's version but what about all the Commands??
wp-cli/wp-cli
We are lucky as WP-CLI repos do not ignore composer.lock so we can use those files to install all packages at versions released.
composer.lock
There is a release blocking problem.
wp-cli/wp-cli-bundle
has these loose constrains: thus we are unable to automatically reconstruct the packages versions at release v2.1.0 etc.What to do know??
It is easy to fix
wp-cli/wp-cli
's version but what about all the Commands??