Version 1.5.1 released

A new release is upon us!

We’re excited to bring you WP-CLI v1.5.1, an intermediary bugfix release with a total of 52 merged pull requests since v1.5.0 in January 2018.

About this release

This is a bugfix release, which means that you shouldn’t expect major feature enhancements. We’re working hard on v2.0.0 which is planned for the summer, and all new features will have to wait for that big one.

Notable features

Yes, I just said not to expect any new features. However, a small number of features managed to sneak into this release nevertheless.

Edit your config files with ease

The config command now has a new config edit function that opens the wp-config.php file in your favorite editor for easy changes. You can configure the editor to be used through the EDITOR environment variable [#48].

Get better insight into your capabilities

Although WordPress is able to have a capability be set to false, to effectively mean an explicit  “deny” of that capability, WP-CLI did not yet show that distinction. It only let you know that the capability was defined, but not whether it was negated, giving the false impression of it being “allowed” instead.

This has now changed, and you can get a complete picture of how the capabilities are set by adding the --show-grant to the cap list command [#19].

Breaking change: Note that the default behavior of cap list has slightly changed because of that. Whereas the previous version showed a capability set to false alongside the normal capabilities, a simple cap list without the new --show-grant flag will now hide the capabilities that are set to false, effectively returning only the capabilities that are actually “granted”.

Bugs that were fixed

Framework

  • Show help text even when proc_(open|close) aren’t available [#4758]
  • Normalize Mac tar output [#4674]
  • Tests should not depend on external commands [#4673]
  • Fix phpunit extractor, glob, behat tests [#4672]
  • Move phpunit PHP directive tests to behat [#4675]
  • Only run phpcs against PHP files on pre-commit hook [#4755]

Commands

  • plugin verify-checksums
    • Make soft change detection more flexible [#41]
    • Add backslash to the regex for matching Windows paths correctly [#39]
  • config
  • package
    • Assume default package name if composer.json file cannot be retrieved [#78]
    • Avoid using Composer CA bundle if in phar [#72]
  • scaffold block
    • Fix theme-specific paths in scaffolded blocks [#137]
    • Modify scaffold block to create index.js [#142]
  • scaffold plugin
    • Exclude tests/test-sample.php via the phpunit.xml.dist file [#134]
  • scaffold plugin-tests | theme-tests
    • Fix WPCS in theme-tests generation [#121]
    • Use correct default $WP_TESTS_DIR on MacOS [#131]
    • Fix sed -i option on MacOS [#132]
    • Switch CircleCI template to CircleCI 2.0 [#115]
    • Add PHP 7.2 to CI templates [#135]
  • search-replace
    • Handle incomplete class (un)serialization gracefully [#76]
    • Handle PCRE errors gracefully [#75]
    • Remove “Site Not Found” message from multisite usage [#69]

Contributors to this release (15 total)

danielbachhuber, emirpprime, ericgopak, felicianotech, gitlost, johnbillion, kshaner, lalaithan, pdaalder, ptrkcsk, salcode, schlessera, stevegrunwell, thrijith, torounit

#release, #v1-5-1

Upcoming bug-fix release 1.5.1

We’re planning a bug-fix release v1.5.1 that is scheduled for Friday, 20th April, 2018.

Here’s the list of bugs we’re planning to fix for this upcoming release:

Given the tight deadline, this list is quite ambitious, and we’d love to have some additional help to make this happen. We’re glad about any contributions (code or otherwise) to help us fix up this list as completely as possible.

UPDATE: You can follow the progression here: https://github.com/wp-cli/wp-cli/issues/4766

#v1-5-1