WP-CLI Release v2.3.0

This release v2.3.0 is, as already announced, rather unspectacular. The previous release was very taxing for several reasons, so we lowered the pace for a while to recover.

This version is mainly meant to finally get a few bug fixes out there that were not critical enough to warrant an immediate hotfix release but are nice to have eradicated at one point, nevertheless.

Overall, a team of 36 contributors has collaborated to get 129 pull requests merged. I’ll briefly go over some of the more noteworthy stuff, but as always, you can also skip directly to the detailed changelog if you prefer.

New command to fix image orientation

Some cameras and smartphones will automatically tag pictures to denote “which way is up”. This means that you will have these devices show you the pictures you took during your handstand in the correct orientation no matter what, even though the actual picture file is upside down.

The media command now has a new subcommand media fix-orientation that reads these special tags and properly applies them to your images. This way, the images will also be shown with the correct orientation on devices that do not support this tag.

You can now skip tables using wildcards

The --skip-tables flag for the search-replace command has learnt a new trick – it now lets you skip a group of tables in one go through wildcards.

You can use wildcards like 'wp_*options' or 'wp_post*' to make your life easier.

Add config settings to the end of the file

Up until now you always had to provide an anchor to attach changes to your wp-config.php to when using the config add command.

You can use this through the special anchor flag --anchor=EOF.

Optimized vagrant support

When you’re connecting to your vagrant VMs through WP-CLI’s special-case vagrant SSH connection scheme, you’ll notice that the operations are way faster now, as we’re caching the configuration across calls now.

Detailed Change Log


  • Permit use of php7.2-mysql and php7.3-mysql in Debian build [#130]


  • Make extraction more robust [#5261]
  • Improve “Adding deferred command…” debug output (Closes: #4893) [#5242]
  • Fix parse_url scheme bug [#5241]
  • Speed up vagrant scheme calls by caching vagrant ssh-config [#5235]
  • Remove bug-provoking test for a bug in WPDB that was fixed [#5220]
  • Fix return types [#5212]


  • Update handbook for release v2.3.0 [#333]
  • Add Fedora and CentOS to installation instructions [#328]
  • Add documentation to integrate Dash/Alfred [#327]


  • Add Romanian language [#329]
  • Update Brazilian Portugues translation [#328]
  • Update Japanese translation [#326]
  • Update French translation [#324]


  • Allow to opt-out from dumping specific sections [#61]
  • Reuse File_Writer for STDOUT support [#60]
  • Make load_export_api() public [#59]


  • Add theme status in wp theme get command [#177]
  • Fix issue with failing test cases due to version mismatch [#181]
  • Fix activation issue of installed plugin/theme [#180]


  • Skip broken test on PHP 7.3 [#178]
  • Investigate include/exclude oddities [#175]
  • Sort translation files by name to ensure same order on all systems [#173]
  • Workaround for parsing dynamic imports [#164]
  • Avoid throwing a notice about strpos(): Empty needle when going through include paths [#149]


  • Skip test for duplicate resizes for core trunk because of bug in current version [#112]
  • Clarify implications of using --skip-copy [#110]
  • Add media fix-orientation command [#108]


  • Adds wildcards support to --skip-tables parameter [#124]


  • Fix port number in example [#58]


  • Add EOF as special-case anchor [#23]


@afragen, @ajoah, @blackfile, @connerbw, @drzraf, @felipeelia, @fernandoherlo, @fuegas, @fullsteamlabs, @gitlost, @greatislander, @herregroen, @hofmannsven, @jrfnl, @l3ku, @localheinz, @maximejobin, @michaelzangl, @MikeWKrystal, @mustafauysal, @ocean90, @ovidiul, @pdaalder, @sagarnasit, @schlessera, @shadyvb, @shashank3105, @siliconforks, @swissspidy, @szepeviktor, @tecking, @thrijith, @vladutilie, @wojsmol, @yognsk, @yousan

#release, #v2-3-0

Release v2.3.0 postponed

The WP-CLI release v2.3.0 needs to be postponed.

The code itself should reliably work right now. However, between Travis server connectivity issues and the Travis PHP environment not being able to connect to the wordpress.org servers, I have been unable to run successful tests over the resulting build (although all local tests pass without issues).

Next planned release date is Tuesday, August 13th. This gives me some time to work through the Travis curl issues and work on getting the project “into the green”.

Upcoming release v2.3.0

Just a quick heads-up regarding the next release for WP-CLI.

WP-CLI v2.3.0 is scheduled to be released on August 7th, 2019, which is a Wednesday according to the calendar I’m looking at.

It will be a pretty unspectacular release, as I will mostly focus on tying up a few loose ends in that particular release and wanted to get a few bug fixes out into the wild.

Expect v2.4.0 (November-ish) to be more feature-rich again… 😊

Thanks to the 2019 sponsors

Maintaining an open source project requires a substantial, ongoing commitment of time and energy. WP-CLI is a dependable tool loved by thousands because it’s actively maintained, which is made possible by the generosity of its sponsors.

For 2019, the following sponsors have stepped forward and directly support the WP-CLI project and ensure it can continue to save both time and headaches to its users:

Please note that, although we’re approaching the middle of the year, these sponsors had already been supporting the WP-CLI project for the majority of 2019 to pick up from the last sponsoring round that ended with 2018. Some legal details that had to be finalized behind the scenes kept delaying this announcement, unfortunately.

If you happen to meet any of their representatives during an event or see that they have a booth, please take a few seconds to say hi and let them know you value their support for the project! 🤗

WP-CLI Release v2.2.0

Phew, it’s finally here! Although there are not that many new features, we had a lot of work being done behind the scenes, to make future releases smoother. A lot of the processes have been improved, and we’ve managed to squash quite a few bugs while doing so.

A team of 57 contributors has collaborated on this release to get 347 pull requests merged. I’ll briefly go over some of the more noteworthy stuff, but as always, you can also skip directly to the detailed changelog or examine the breaking changes section if you’re impatient.

New Committer

  • Thrijith Thankachan (@thrijith) is from Surat, India. He works for rtCamp as a WordPress Engineer and he is the developer behind the two new commands alias and maintenance-mode.

WP-CLI code standard

Through the initiative of @jrf, and with the outstanding help from @thrijith, @wojsmol & @williampatton, we now have a WP-CLI code standard that we can enforce.

For any package, you can just run composer phpcs to verify that your code meets the CS requirements. Basic formatting issues can be automatically corrected through vendor/bin/phpcbf (a Composer script will soon follow for that).

The goal of this big effort is to reduce the back & forth on pull requests and thus reduce the maintenance burden. For most pull requests, whitespace issues and code style issues represent the bulk of the time and effort required by the maintainers. With enforced and automated coding standards, everyone saves time and the discussion more often revolves around the actual logic that solves the problem, instead of alignment issues and spacing rules.

This is all pretty fresh, so stay tuned while more extensive documentation and updates to the tooling will follow.

New command to manage aliases

The old wp cli alias has finally grown up and has become a complete CRUD interface for managing your WP-CLI aliases. You can alias list to retrieve your current configuration, alias get to retrieve an individual alias, and alias add|update|delete to make changes.

While experimenting with these commands, please remember that you need to work around the already active global parameters. This is why we had to add a prefix (--set-<flag>) to all the flags that let you configure the aliases. So, updating the SSH connection string for an alias is done through alias update <key> --set-ssh=<ssh>. If you would use --ssh instead to configure it, you’d actually immediately connect to that SSH target instead.

# List alias information.
$ wp cli alias list
@all: Run command against every registered alias.
  user: wpcli
  path: /Users/wpcli/sites/testsite

# Get alias information.
$ wp cli alias get @dev
ssh: dev@somedeve.env:12345/home/dev/

# Add alias.
$ wp cli alias add prod --set-ssh=login@host --set-path=/path/to/wordpress/install/ --set-user=wpcli
Success: Added '@prod' alias.

# Update alias.
$ wp cli alias update @prod --set-user=newuser --set-path=/new/path/to/wordpress/install/
Success: Updated 'prod' alias.

# Delete alias.
$ wp cli alias delete @prod
Success: Deleted '@prod' alias.

New command to control maintenance mode

WP-CLI now lets you enable or disable the WordPress maintenance mode with the two simple commands maintenance activate and maintenance deactivate. You can query the current status with maintenance status (for humans) or maintenance is-active (for easy shell scripting).

# Activate Maintenance mode.
$ wp maintenance-mode activate
Enabling Maintenance mode...
Success: Activated Maintenance mode.

# Deactivate Maintenance mode.
$ wp maintenance-mode deactivate
Disabling Maintenance mode...
Success: Deactivated Maintenance mode.

# Display Maintenance mode status.
$ wp maintenance-mode status
Maintenance mode is active.

# Get Maintenance mode status for scripting purpose.
$ wp maintenance-mode is-active
$ echo $?

WP-CLI “binaries”

The eval-file had a small, innocuous tweak. When it encounters a “shebang“, a first line in a file that starts with #!, it will strip that line and try to run the rest of the file through PHP’s eval().

For folks not used to working in Unix shells, that might sound rather useless, but this shebang is actually a construct that your shell understands, and that lets you tell the shell how to execute the file.

As an example, here’s a file that contains such a shebang and actually points to WP-CLI’s eval-file command:

#!/bin/env wp eval-file
echo get_bloginfo('name');

With that file structure, you can now rename that script file to something like blogname and make it executable. It now behaves like any other shell tool, and will use WP-CLI as a shell framework for retrieving the current blog’s name.

Have fun experimenting with this new functionality, and don’t forget to share the more interesting use cases you can think of with the rest of the community!

Breaking changes

Name changes

While going through the code to make it fit for actually enforcing our new WP-CLI coding standard, we decided to rename some of the more internal functions, methods and properties to make the experience more consistent.

Although we took great care to figure out what we could safely rename and what needed to stay intact, there might be some edge cases where people are nevertheless directly coupling to some bit of internal code.

This is mostly relevant if you extend one of the WP-CLI classes to override default behavior.

Removal of framework files from test package

The test package included a few framework files that were used to make the FeatureContext logic work. However, as wp-cli/wp-cli was a hard requirement for wp-cli/wp-cli-tests anyway, we removed these framework files and had the test package pull them in through the dependency.

In case you were directly coupling your code to these files as they were found in wp-cli/wp-cli-tests (which is unlikely), then you’ll have to change your code to refer to these same files in the wp-cli/wp-cli package. See the pull request for more details.

Consistent display of serialized meta values

Serialized data has been displayed very inconsistently, with some commands showing them as is (option list), and some commands unserializing them automatically for display (post meta list).

We’ve changed this so that they all show the values as they are stored, to avoid surprises.

This is a breaking change, however, and if you happened to rely on the automatic unserialization, you’ll be glad to hear that the affected commands now provide an optional --unserialize flag to get back to the old behavior. You can even put this flag into your global config to permanently stick with the old behavior.

Affected commands are: comment meta get|list, network meta get|list, post meta get|list, user meta get|list.

Complete change log

All repositories

  • Implement CS checking based on the WP_CLI_CS ruleset
  • Add PHP 7.3 to Travis CI build matrix
  • Move PHP 5.4 tests from WP_VERSION=latest to 5.1


  • Bundle new maintenance-mode command [#113]
  • Add a GitHub setting for label to dependencies.yml [#74]
  • Try removing “ignore-platform-reqs” from Dependencies.yml [#72]
  • Add dependencies.yml file to define auto-updates [#70]


  • Always reattach subcommands [#5203]
  • Add warning message to let the user know when WP_CLI_SSH_PRE_CMD is in use [#5197]
  • Add aliases subcommand for backwards compatibility [#5194]
  • Avoid double registration of commands [#5193]
  • Add default titles to release checklists [#5168]
  • Limit ranges of PHP versions in Composer [#5142]
  • Add checklists for regular and patch releases [#5141]
  • Add flags to include / exclude views in wp_get_table_names() [#5128]
  • Internalize array_column() shim, because package is abandoned [#5126]
  • Add command to manage aliases [#5122]
  • Introduce ability to override wp-config.php path with env var WP_CONFIG_PATH [#5119]
  • Support persistent MySQL connections [#5115]
  • Fixed documented return type for make_progress_bar() [#5112]
  • Fix FileCache::export() not ensuring parent directories exist for $target [#5103]
  • Switch ext-readline to ‘suggest’ instead of a hard requirement [#5102]
  • Update docblock for add_command() to properly reflect the return value [#5099]
  • Fix failing test under WP 5.1 [#5094]
  • Update parse_str_to_argv() regex to be more accurate [#5090]
  • Update ISSUE_TEMPLATE [#5078]
  • Ensure cache directories are accessible [#5068]
  • Add dependencies.yml file to define auto-updates [#5066]
  • Add WP_CLI::has_config() method [#5063]
  • Change to “Happy publishing.” per change in core [#5059]
  • Adapt outdated links in ISSUE_TEMPLATEfile [#5056]
  • Fix typo: Autolaoder => Autoloader [#5055]


  • Update example of wp config create [#317]
  • Update link of backwpup plugin [#315]
  • Update release checklist documentation to point to the issue templates [#306]
  • Add wp cli info as first environment info [#305]
  • Document the <scheme> part of the --ssh flag [#299]
  • Add documentation for the --foo[=<bar>]to command-cookbook.md [#293]
  • Document WP_CLI_CUSTOM_SHELLenvironment variable [#292]
  • Change references to paths being in .bash_profile to .bashrc [#290]
  • Update roadmap [#287]
  • Add instructions for checking additional configuration files for PHP memory_limit[#286]
  • Update the ‘using a custom PHP binary’ link [#285]
  • Update hosting-companies.md [#284]
  • Update link to command list in Quick Start [#282]
  • Add a note about potential connection issues when using MySQL >= 8.0. [#280]
  • Composer installation instructions are dated and incorrect [#279]
  • Update broken links on Command Cookbook page [#276]


  • Switch to githubusercontent per other submission [#322]
  • pt_BR – Version update and minor adjustments [#321]
  • Redirect blog to site [#320]


  • Make soft change detection more flexible [#41]
  • Add backslash to the regex for matching Windows paths correctly [#39]


  • Update template based on latest version [#88]
  • Change Happy blogging. to Happy publishing. in wp-config.php template [#82]


  • Replace instances of wp.dev with example.com [#115]
  • Change to “Happy publishing.” per change in core [#103]


  • Modify tests to correctly verify --force-regex flag [#50]


  • Allow deleting multiple options at once [#247]
  • Fix logic error in presence of ‘site meta’ check [#244]
  • Add count to post-type and taxonomy commands [#241]
  • Reset option value to default for privacy policy on site empty [#236]
  • Migrate term from a taxonomy to another one [#234]
  • Include ‘supports’ field when fetching a single post type [#233]
  • Check for STDIN if --post_content is used [#189]
  • Rename phpunit.xml to phpunit.xml.dist [#252]


  • Strips out #! /bin/bash and similar at the beginning of PHP files [#35]
  • Fix handling of __FILE__ and __DIR__constants in eval()‘d code. [#38]


  • Identify non-writable directory as such [#54]


  • Add the --page parameter to the theme search command [#167]
  • Allow deleting the currently active theme [#158]
  • Display warning in plugin list info if plugin version is higher than expected [#157]
  • Fix success message example on plugin uninstall [#148]
  • Handle extension activation for WP error or extension not found [#146]


  • Set Language header directly to prevent exceptions [#150]
  • Fix make-pot tests [#135]
  • Add script file name to JSON translation files [#134]
  • Improve language handling when creating JSON files [#133]
  • Add support for nested theme folders [#130]
  • Prevent possible PHP notice in IterableCodeExtractor [#129]
  • Extend PotGenerator to improve plural forms output [#128]
  • Remove project header comments for comments audit [#123]


  • Change LanguagePackUpgrader::download_packagesignature [#82]


  • Refactored aspects of the image collection and determination of sizes [#103]


  • Adapt framework requirement [#103]


  • Update success message position [#29]


  • Add --show-grant argument to cap list and --grant to cap add[#19]
  • Add --field=<field> support to listing roles [#17]


  • Prevent creating unregisterable blocks due to invalid plugin slug [#203]
  • Add dependencies.yml to plugin .distignore [#202]
  • Add DeployHQ .deployignore to ignored files in .distignore [#201]
  • Ignore various JavaScript config files in plugin .distignore [#200]
  • Update links to blocks documentation [#199]


  • Swapped out the .dev Google TLD for the .test RFC protected domain in doc examples [#107]


  • Better explain the --basic flag [#23]
  • Close already opened process while prompting [#36]
  • Add possibility to change the shell binary [#33]


  • Fix a bug where adding superadmins would crash if none existed before [#22]


  • Fix parsing of escaped quotes [#16]
  • Normalize the newline to prevent an issue coming from OSX [#14]
  • Change to “Happy publishing.” per change in core [#13]
  • Add .gitattributes file [#12]



#release, #v2-2-0

X-post: The Get Involved table at WCEU 2019

X-comment from +make.wordpress.org/community: Comment on The Get Involved table at WCEU 2019

Upcoming release v2.2.0

There’s a new release in the making: WP-CLI v2.2.0 is scheduled for Wednesday, April 24th, 2019.

We already have a lot of nice improvements in the pipeline, but there’s still time to have your code included if you want to be a part of that release:

I will prioritize the bugs and some of the more important issues into a checklist for the upcoming release that will be available for WordCamp London, so I hope to see many, many people join us for the Contributor Day on April 5th.

Random note: The scheduled date for the v2.2.0 release coincides with the Contributor Day for WordCamp Paris. Maybe we can arrange for something special on that day?

WP-CLI PHP Requirements Strategy

Up until now, WordPress Core was keeping a very low PHP minimum requirement, to support as many legacy server platforms as possible. As a result, WP-CLI tried to stay as low as possible with its own PHP minimum requirement, within reason. It made sense to not randomly break support for people stuck on lower PHP versions if we could easily avoid it.

WordPress Core is now planning to switch to a different approach for dealing with minimum PHP requirements, as recently announced on the Make/core blog: “Updating the Minimum PHP Version”.

As soon as WordPress Core has moved past WP-CLI in terms of minimum PHP version, we will try to adapt WP-CLI, but with a 1-year delay at the least. This delay is meant to allow site owners to still use WP-CLI to migrate their old sites over to newer servers. One year of additional support should be ample time to work on migrating your server over from an unsupported PHP platform.

After this year, we might raise the minimum as well, or wait for a more strategic moment to do so.

So this will be the guarantee that WP-CLI provides moving forward: Whenever WordPress Core raises the PHP minimum version requirement past WP-CLI, WP-CLI will stay at the old minimum requirement for at least 1 full year.

Given the current plans put forth in the above announcement, and considering the fact that there’s no real benefit to be had for WP-CLI to bump the requirement twice, the preliminary plan is to schedule WP-CLI v3 with PHP 7+ as a minimum requirement for December 2020.

The final announcement for a WP-CLI v3 release date will be done at a later date, probably closer to the end of this year.


WP-CLI v2.1.0 Release Notes

‘Tis the season to celebrate a new release of WP-CLI! 🎄 A total of 39 contributors has collaborated on this release to have a staggering 293 pull requests merged. We’ll go over the main areas now, but you also skip directly to the detailed changelog or ponder over the breaking changes section if you’re impatient.

i18n – round two!

The recent i18n make-pot command has replace the old make-pot tool in WordPress Core and is now the official translation build tool for the Core. This effort has lead to numerous improvements to make it both more robust and more flexible. Amongst the more notable changes, it can now parse JavaScript in addition to the PHP files, and together with the new i18n make-json command that lets you produce separate JSON files, you’re all set to make your Gutenberg blocks translatable!

Translation pack improvements

We didn’t stop there with regards to making WordPress an “international success”… the language family of commands got several improvements and fixes. The most notable one is that language plugin|theme update now understands an --all flag, so you can update language packs for all your installed plugins/themes in one go.
# Update the language packs for all plugins.
$ wp language plugin update --all
Updating 'Japanese' translation for Akismet 3.1.11...
Downloading translation from https://downloads.wordpress.org/translation/plugin/akismet/3.1.11/ja.zip...
Translation updated successfully.
Updating 'Japanese' translation for Contact Forms 7 4.2.1...
Translation updated successfully.
Success: Updated 2/2 translation.

Partial prompting

The lesser known --prompt global parameter has now become even more useful. Instead of always prompting for all arguments, it skips those that were already provided, as you would probably already have expected. One way this can be used is to prefill all arguments that you can remember and then use --prompt to help you with the more arcane flags. More importantly, though, you can now prefill all the arguments that are already known inside of a script, and then add the --prompt argument to let the script query the remaining information from the user.

Manage the WP-CLI cache

We added two additional commands that let you manage the WP-CLI internal cache. cli cache clear will clear the entire cache, whereas cli cache prune will only clear the elements known to be stale. This latter will for example remove all the versions of WP core that you downloaded except for the most recent one.
# Remove all cached files.
$ wp cli cache clear
Success: Cache cleared.

# Remove all cached files except for the newest version of each one.
$ wp cli cache prune
Success: Cache pruned.

Better control over transients

You can now list the current transients on your site or network using the filterable transient list command. You can search for specific transients or exclude the ones you want to hide. You can even choose whether you want the expiration to be displayed in a human-readable or machine-parseable format.
# List all transients
$ wp transient list
| name | value | expiration    |
| foo  | bar   | 39 mins       |
| foo2 | bar2  | no expiration |
| foo3 | bar2  | expired       |
| foo4 | bar4  | 4 hours       |
Furthermore, transients are now handled more consistently across multisite networks, and allow you to properly distinguish between regular transients and site transients.

Database management improvements

Also, the db size loved the idea of a --human-readable flag like in the transient list command so much that it got its own version. This will always use the unit that is best adapted to convey the information.
# List the size of the database in a human-readable form
$ wp db size --tables --human-readable
| Name    | Size   |
| my_site | 117 MB |
Furthermore, the db import command now understands all the flags that the mysql binary does, so that you can get past errors in SQL exports or adapt the result you want to see in your target site.
# Import an SQL export file that contains errors, by
# passing the --force argument to mysql binary.
$ wp db import export-with-errors.sql --force
Success: Imported from 'export-with-errors.sql'.

Smarter configuration

The config commands are now smarter. They not only allow you to edit the wp-config.php even on a broken WordPress installation, but you’re also able to retrieve the individual settings in whatever format best fits your scripting needs. Finally, adding new configuration values or updating existing ones will now only throw errors in the most ambiguous scenarios, while they just work for the majority use cases without the need to explicitly specify a --type.

Checking the existence of a post

You can now check whether a given post exists by using the new post exists command. It returns a shell exit code, so you can use it directly in shell conditionals.
if wp post exists 42; then
   echo "Skipping post import for ID 42, it already exists."
   echo "Importing post with ID 42..."
   # ...

Breaking changes

  • While we had already bumped the minimum PHP version in v2.0.0 and started using PHP 5.4+ code in some places, we now actively enforce this requirement in the bootstrapping code [wp-cli#5039](https://github.com/wp-cli/wp-cli/pull/5039).
  • The restructuring of the packages in v2.0.0 produced a regression which caused overrides through the package manager to not work anymore. We fixed this by completely ripping the framework out of the regular Composer autoload flow. This should now lead to less surprises when rearranging the Composer compositions, but might have side-effects in some exotic Composer setups [wp-cli#5010](https://github.com/wp-cli/wp-cli/pull/5010).
  • The breaking change from v2.0.1 to throw an error for non-lowercase theme slugs was reverted, as it broke far more than we anticipated. That’s why we now break the breaking change to get back to the original behavior [extension-command#137](https://github.com/wp-cli/extension-command/pull/137). 😛
  • WP-CLI tries to speak proper English now. To achieve this, we changed the output to use the real world “installation” where we were using the fantasy term “install” before [wp-cli#4946](https://github.com/wp-cli/wp-cli/pull/4946).

Complete change log


  • Bump PHP version to 5.4+ for PHP Compatibility Checker [#63]
  • Bump included package-command to v2.0.3 [#35]
  • Remove .behat-progress.log [#25]
  • Use dev-master for framework instead of tagged release [#24]
  • Add replace-label maintenance command [#17]


  • Properly reorder synopsis passed in via $args [#5049]
  • Bump PHP version check in bootstrap code to v5.4+ [#5039]
  • Remove ext-posix requirement from Composer file [#5038]
  • Fix override test on Composer stack [#5036]
  • PHP 7.0+: allow for changed list assignment order [#5021]
  • Skip associative arguments that were already provided on --prompt [#5015]
  • Bump PHP version to 5.4+ for PHP Compatibility Checker [#5014]
  • Use custom autoloader to load framework [#5010]
  • Add extension requirements to composer.json file [#5001]
  • Add ext-zip as suggested extension [#4998]
  • Fix parsing of arguments for WP_CLI::runcommand() with launch=false [#4989]
  • Match the way WordPress Core locates wp-config.php [#4984]
  • Use dirname() instead of .. to locate wp-config.php to match Core behavior [#4963]
  • Update README to account for the 280-character limit on Twitter [#4962]
  • Use “installation” instead of “install” in documentation [#4960]
  • Bump included package-command to v2.0.3 [#4957]
  • Reattach existing subcommands from namespace to replacing command [#4951]
  • Convert ‘install’ to ‘installation’ [#4946]
  • Add sibling vendor folder location [#4938]
  • Check and display help command if requested [#4928]
  • Fix var_export return in WP_CLI::print_value [#4926]
  • Adapt README.md file for v2.0.1 release [#4924]
  • Bump version to 2.1.0-alpha [#4898]
  • Added cli cache prune & cli cache clear commands [#4787]


  • Add Savvii to hosting companies [#267]
  • Update hosting-companies.md [#266]
  • Update the set up and testing flow [#265]
  • History | grep = even better than ctrl-r [#263]
  • Please add One.com to the list [#261]
  • Add lima-city to hosting companies [#258]
  • Add plugin Simple History [#257]
  • Update running-commands-remotely.md to add ~/bin approach [#256]
  • Use “installation” instead of “install” [#255]
  • Fix issue with broken filename [#253]
  • Document root cause to STDOUT PHP notice [#252]
  • Update with v2 changes [#251]
  • Remove WP_CLI_Command class [#250]
  • Include the cron jobs in the governance document [#248]


  • Updated index.md – Spanish version [#316]
  • Adapt index.md file for v2.0.1 release [#315]


  • Rename transient list method to be consistent with other list commands [#49]
  • Introduce a list command to list all transients [#48]
  • Make output of transient type generic to include multisite behaviour [#47]
  • Replace usage of global with wp_using_ext_object_cache() [#45]
  • Improve deleting site transients [#42]


  • Use command namespaces instead of conditional addition [#54]


  • Permit use of wp config edit when WP isn’t functional [#71]
  • Use constant as default type when adding new keys [#80]
  • Add --format option for config get command [#79]
  • Use print_value() instead of log() for output of config get [#78]


  • Switch to wp-cli@dev [#92]
  • Adapt install => installation in tests [#90]
  • Fix tests for uncached nightly downloads [#100]
  • Adapt framework requirement [#101]


  • Make sure WP Cron is enabled for cron tests [#36]


  • Fix comment argument test [#127]
  • Adds --human-readable parameter to db size command [#124]
  • Support all mysql flags while importing database [#123]
  • Add search and delete example [#122]
  • Add new db clean to README.md and configuration files [#119]
  • Fix combination of --format & --size_format flags [#118]
  • Add links to mysql documentation [#117]


  • Update readme [#204]
  • Bump site meta test requirement to WP 5.1+ [#225]
  • Add missing --description flag logic for user create [#217]
  • Expose the available query variables for comment and post queries [#213]
  • Use “installation” instead of “install” [#212]
  • List all entities in the package description [#208]
  • Bail with a warning when deleting custom post types without --force [#188]
  • Add post exists command [#182]


  • Adapt install => installation in tests [#33]


  • Throw error in theme fetcher on non-lowercase slugs [#126]
  • Raise timeout for HTTP requests to 1 minute [#125]
  • Revert “Throw error in theme fetcher on non-lowercase slugs” [#137]
  • Failed plugin updates now throw errors [#143]
  • Use “installation” instead of “install” [#139]
  • plugin delete <plugin-name> not working if path has a space or & in it [#138]


  • Require framework as hard dependency [#78]
  • Add Composer config settings [#74]
  • Improve detection of translator’s comments [#101]
  • Improve regex replacement [#100]
  • Replace regexes Peast can’t parse [#99]
  • Allow skipping strings audit [#94]
  • Update file-comment argument docs [#93]
  • Set a placeholder PO-Revision-Date header [#92]
  • Remove ‘foo’ file [#88]
  • Include should override exclude instead of the other way around [#87]
  • Support parsing minified JS files created by WebPack [#85]
  • Add unit test cases for include/exclude options [#83]
  • Allow passing an empty file comment [#82]
  • Determine includes and excludes based on scores [#104]
  • Add parsing of .js.map files to improve reliability of JS translations [#103]
  • Remove second argument to WP_CLI::success() [#112]
  • Normalize paths [#111]
  • Normalize paths [#110]
  • Add i18n make-json command [#109]


  • Make sure upgrader strings are always in English [#54]
  • Slug fixes [#53]
  • Change access to activate_language() to private [#47]
  • Don’t error when a translation is not yet available [#69]
  • Check if array key exists to prevent undefined index notices [#67]
  • Support installing translations for all installed plugins/themes [#64]
  • Make use of report_batch_operation_results() for install commands [#63]
  • Continue if $available_updates is not a array [#62]
  • Add tests for wp site switch-language [#57]


  • Fix SVG regeneration test by adding an XML header to fake SVG file [#98]


  • Make tests work with both install and installation strings [#100]


  • Use forced width attribution as fallback only to avoid scrapping manual widths [#136]
  • Fix incorrect namespace for cli\notify\xxx [#137]


  • PHPCS template: fix XML error in ruleset [#171]
  • Add textdomain to block strings and update tests accordingly [#187]
  • Use branch for WP_TEST_TAG for RC and beta [#186]
  • Missing text domain in post_type_extended.mustache [#184]
  • Work around Travis CI issue with _s download certificate [#182]
  • Fix typo in Travis config [#180]
  • Ignore ‘node_modules’ in PHPCS XML file [#178]
  • Allow for installation as well as install [#177]
  • Fix syntax error in block-php.mustache [#176]
  • Inc ‘menu_position’ when scaffolding a post type [#173]
  • Remove Inflector Class [#172]
  • Run docker-php-ext-install with sudo -E in CircleCI [#188]
  • Split up the list of expected files to allow for WP 5.0+ changes [#195]


  • Corrects NULL export values. [#93]


  • Set SERVER_ADDR for the built-in webserver [#49]


  • Add regression test for #5 [#8]
  • Remove colloquialism [#6]
  • Preserve leading whitespace characters on config update [#5]
  • Fix regex for closing syntax in string [#9]
  • Use real config filename in Exception messages [#11]


Please give a big round of applause to these fine folks that have contributed their time and expertise to make this release possible: @abhijitrakas, @antigenius, @austinginder, @BhargavBhandari90, @birkestroem, @bitwombat, @bonny, @Calinou, @danielbachhuber, @dgroddick, @emirpprime, @fjarrett, @frozzare, @GaryJones, @Grucqq, @henrywright, @herregroen, @insomnux, @jrfnl, @KushibikiMashu, @markjaquith, @MoisesMN, @Mte90, @ocean90, @phillipp, @pmgarman, @rmccue, @siliconforks, @soulseekah, @swissspidy, @szepeviktor, @thrijith, @torounit, @tsmith1, @VladimirAus, @wojsmol, @yahilmadakiya, @yousan Thank you! ❤️

#release, #v2-1-0

WP-CLI v2.1.0 release postponed

The WP-CLI v2.1.0 release was originally scheduled for November 6th, 2018. However, due to the current timeline of the WordPress 5.0 release and the additional pressure it puts on all parties involved (WP-CLI contributors & testers included), I decided to postpone the release.

The new planned release date will be Tuesday, December 18th, 2018. This will keep it away from the planned release date(s) of WordPress 5.0 and place it shortly after the contributor day at WordCamp US, allowing us to get bug fixes & improvements done that day into the release as well.

For people who are waiting on getting their hands on the v2.1.0 release because of bugs in v2.0.1 that will be fixed, please note that you can always upgrade to the latest nightly release with the command wp cli update --nightly and switch back to stable releases later on with wp cli update --stable.