Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Release Checklist

Daniel Bachhuber edited this page · 19 revisions

This page describes the list of activities that developers must perform to produce a new release of WP-CLI.

Updating WP-CLI

Make sure that the contents of VERSION are changed to latest. The file must not have any trailing whitespace.

Locking php-cli-tools version

php-cli-tools is set to dev-master during the development cycle. During the WP-CLI release process, composer.json should be locked to a specific version. php-cli-tools may need a new version tagged as well.

Updating the contributor list

Use ./utils/contrib-list to see new contributors. Update the .mailmap file so that the names match their github handles.

When done, use sort .mailmap -f -u -o .mailmap to only add new contributors.

Updating the Phar build

1) Create a git tag and push it.

2) Create a stable Phar build:

cd wp-cli-builds/phar
cp wp-cli-nightly.phar wp-cli.phar
md5 -q wp-cli.phar > wp-cli.phar.md5

3) Create a release on Github: https://github.com/wp-cli/wp-cli/releases. Make sure to upload the Phar from the builds directory.

Updating the Debian build

1) Run this script: https://github.com/szepeviktor/wplib/blob/master/bin/wp-cli-updatedeb.sh

2) Commit file to builds repo

Updating the Homebrew formula

A pull request must be submitted to the Homebrew repo. See https://github.com/Homebrew/homebrew-php/pull/1687#issuecomment-98408399 for background.

Updating the website

See https://github.com/wp-cli/wp-cli.github.com#readme

Writing the release post

Use ./utils/contrib-list -l to generate the list of contributors.

Something went wrong with that request. Please try again.