Opened 7 years ago
Closed 7 years ago
#41472 closed defect (bug) (fixed)
Travis CI: Use the latest PHPUnit 6.x branch
Reported by: | netweb | Owned by: | johnbillion |
---|---|---|---|
Milestone: | 4.9 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | |
Focuses: | Cc: |
Description
Follow up to #39822 / [40536] where PHPunit 6.x support was added to use PHPUnit 6.1 for Travis CI PHP 7.x versions
PHPUnit 6.2 was released 2nd June 2017, and the latest 6.2.3 released 3rd July 2017
We should use the latest 6.x branches rather than the 6.1.x branch
Here's a Travis CI job testing this patch as at current SVN revision [41179]
https://travis-ci.org/ntwb/wordpress/builds/258400758 via https://github.com/ntwb/wordpress/pull/4
Attachments (4)
Change History (20)
#3
@
7 years ago
Thanks @ayeshrajans, hadn't seen this until you mentioned it, cheers +1
Refreshed patch uses ^6
and ^4
to use latest PHPUnit 6.x and 4.x respectively where required
https://semver.mwl.be/#?package=phpunit%2Fphpunit&version=%5E6&minimum-stability=stable
https://semver.mwl.be/#?package=phpunit%2Fphpunit&version=%5E4&minimum-stability=stable
#4
@
7 years ago
- Owner set to johnbillion
- Status changed from new to reviewing
I'm confident in PHPUnit's ability to follow semver without breaking compatibility within a major version, so let's do this.
I'm sorry if I'm missing something. Can't we
composer global require phpunit/phpunit:^6.2
?Composer lately started to recommend the caret operator, and it should pick the latest available release. The patch #1 with asterisk should be functionally the same, but caret is a lot more commonly used in the documentation.
Ref: https://getcomposer.org/doc/articles/versions.md#caret-version-range-