Fix compatibility with newer Composer versions #183
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #172
Supersedes wp-cli/wp-cli#5757
This PR adds a compatiblity shim for
ComposerIO\NullIOso that it works with Composer 2.3+ which added type declarations and thereby changed method signatures and broke BC.This PR moves the
ComposerIOclass over from thewp-cli/wp-cli. This seems to have been a left-ver from when the original WP-CLI monorepo was split up.The PR also removes the upper limit on the Composer version now, and was successfully tested with Composer 2.6+.
Props to @stefanfisk for a lot of the initial digging and work on the previous PR.