#8381 closed defect (bug) (fixed)
Some composer dependencies fail to install with composer v2.0.0
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 8.0.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Cc: |
Description
It only happens for PHP 5.6 jobs.
For now, I will include a quick fix to .travis.yml
to rollback to composer v1.10.16.
But I believe we should look into it more deeply during next release.
Attachments (3)
Change History (14)
This ticket was mentioned in Slack in #buddypress by slaffik. View the logs.
4 years ago
#5
@
4 years ago
- Keywords has-patch added
In 8381.patch, I'm making sure all dependencies are installed by updating them to their compatible versions with composer v2.0+. I'm also taking this opportunity to add the phpunit/phpunit
dependency to be able to run PHP Unit tests with version 8.0 of PHP.
To test PHP 8.0 using @wordpress/env, you then simply need to run:
composer update
export WP_ENV_PHP_VERSION="8.0"
npm run wp-env start
npm run test-php:composer
ornpm run test-php-multisite:composer
We should then be able to use @wordpress/env to create a first GitHub action to test PHP 8.0 see #8421
#6
@
4 years ago
- Keywords commit added
I believe 8381.2.patch is our way forward with Composer v2. The main difference with first patch is that it uses the PHPUnit composer version for all tests. It allows us to test PHP 7.x and PHP 8.0. It will also fix #8420
I'm going to commit it asap.
#8
@
4 years ago
- Keywords commit removed
- Resolution fixed deleted
- Status changed from closed to reopened
I'm reopening this ticket as Travis doesn't like too much the changes I've introduced in .2.patch. I believe .3.patch should satisfy Travis & @wordpress/env
. I still need to test @wordpress/env
to check it doesn't introduce regressions.
In 12766: