-
Notifications
You must be signed in to change notification settings - Fork 23
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
Properly support @require-wp-latest
#190
Comments
@swissspidy This is perpetually skipped - see wp-cli-tests/utils/behat-tags.php Lines 46 to 60 in 560ed5c
|
Yeah I saw that code too. The thing is:
|
@require-wp-latest
does not seem to work@require-wp-latest
I'd suggest we actually remove
I only see one use: https://github.com/search?q=org%3Awp-cli%20require-wp-latest&type=code Are there others? |
I think you're right! I just double checked and I just saw tons of duplicates in all the different I suppose it not even working shows how unnecessary it can be in that test there. |
Bug Report
Describe the current, buggy behavior
I spotted a few instances of
@require-wp-latest
in our code base, but I don't think it actually works. At least that wasn't the case when I tried it at wp-cli/doctor-command#165run-behat-tests
already grabs the latest version of WordPress, so when we do things likeWP_VERSION=6.2 composer behat
, it could pass this info on tobehat-tags.php
so that the script knows that 6.2 is lower than the current latest.Describe what you would expect as the correct outcome
@require-wp-latest
works as expectedProvide a possible solution
Provide additional context/Screenshots
The text was updated successfully, but these errors were encountered: