Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Composer 2.5 #172

Closed
danielbachhuber opened this issue Feb 20, 2023 · 8 comments · Fixed by #183
Closed

Support for Composer 2.5 #172

danielbachhuber opened this issue Feb 20, 2023 · 8 comments · Fixed by #183

Comments

@danielbachhuber
Copy link
Member

We should update wp-cli/package-command so it can be installed where composer/composer 2.5 is a dependency.

From #167 (comment)

Done is:

  • wp-cli/package-command supports composer/composer:~2.5.
@stefanfisk
Copy link

@danielbachhuber do you know anything specific that needs fixing, or is it just untested?

@danielbachhuber
Copy link
Member Author

@stefanfisk I think some fixes are needed for this: https://github.com/wp-cli/package-command/actions/runs/4189588371/jobs/7262087460#step:13:318

@stefanfisk
Copy link

@danielbachhuber cool, that looks easy enough. Is it OK to go with only ^2.5.4, or is ^1.10.23 still needed as well?

@danielbachhuber
Copy link
Member Author

@stefanfisk We can remove ^1.10.23 as long as there aren't any backwards-compat issues.

@stefanfisk
Copy link

@danielbachhuber so after making the changes required I found some old related issues where this exact change was abandoned because Composer 2.3 is not compatible with PHP 5.6: #151 #152

So as long as PHP 5.6 compatibility is required this is not fixable. I'm not familiar with the PHP compatibility policy for WP-CLI, is PHP 5.6 compatiblity still required? And if it is, is there any end date for said compatiblity requirement? 5.6 is absolutely ancient by now :/

@danielbachhuber
Copy link
Member Author

so after making the changes required I found some old related issues where this exact change was abandoned because Composer 2.3 is not compatible with PHP 5.6:

@stefanfisk Ah, good find.

So as long as PHP 5.6 compatibility is required this is not fixable. I'm not familiar with the PHP compatibility policy for WP-CLI, is PHP 5.6 compatiblity still required? And if it is, is there any end date for said compatiblity requirement? 5.6 is absolutely ancient by now :/

We'll need to support support PHP 5.6 at least as long as WordPress core supports 5.6. Fortunately, that should be over soon.

In 2019, our plan was to support PHP 5.6 for at least a year after core removed support. It seems like we may need to revisit that, though.

@stefanfisk
Copy link

As a workaround, I switch from wp-cli-bundle to requiring the individual packages except for package-command.

It's a bit ugly, but would you be OK with having to implementations of ComposerIO, one with types and one without, and then have ComposerIO.php require the correct one based on PHP_MAJOR_VERSION?

@danielbachhuber
Copy link
Member Author

It's a bit ugly, but would you be OK with having to implementations of ComposerIO, one with types and one without, and then have ComposerIO.php require the correct one based on PHP_MAJOR_VERSION?

@stefanfisk Yes, that would be a perfectly fine approach

oxyc added a commit to generoi/bedrock that referenced this issue Jul 17, 2023
See wp-cli/package-command#172 for
wp-cli/bundle fork reason
oxyc added a commit to generoi/bedrock that referenced this issue Jul 17, 2023
See wp-cli/package-command#172 for
wp-cli/bundle fork reason
oxyc added a commit to generoi/bedrock that referenced this issue Jul 17, 2023
See wp-cli/package-command#172 for
wp-cli/bundle fork reason
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants