3.0.5

New --yes flag for deploy skips the "Would you really like to deploy" confirmation, e.g. vendor/bin/wp-sync-deploy deploy production run --yes.

3.0.4

Before deploying, wp-sync-deploy now asks for confirmation if the remote WordPress version is newer than the local one (e.g. after a security update applied on the server), preventing accidental downgrades.

3.0.3

Before each run, wp-sync-deploy now checks if an important update is available and asks for confirmation before proceeding with an outdated version.

3.0.2

Documented that options like --config or --paths passed to composer script aliases need a -- separator.

3.0.1

Updated the package description.

3.0.0

This tool is now available through composer

That's the new recommended way to install it.

2.3.2

Fix: deploys failing against older rsync on the server

Since 2.3.1, deploys could abort when the remote server runs an older rsync (e.g. 3.1.3):

ERROR: rejecting excluded file-list name: public/core
rsync error: protocol incompatibility (code 2) at flist.c(912) [receiver=3.1.3]

The new protect rules (P /public/*) also matched the deployed paths themselves, which older receivers treat as excluded. Deployed paths and their parents are now explicitly exempted, while undeployed files like wp-config.php, index.php and uploads stay protected.

Also fixed for nested deploy paths (e.g. core at public with content at public/content): stale files in the outer directory are deleted again, and those setups no longer hit the same error.

⚠️ 2.3.1 – Update Now!

⚠️ Update immediately

Recent macOS versions ship openrsync as /usr/bin/rsync. It ignores some of the filter rules wp-sync-deploy relies on,
so --delete can permanently delete protected files on your remote server.

This release refuses to run unless GNU rsync 3.x is available.

composer update hirasso/wp-sync-deploy
brew install rsync   # macOS

2.3.0

• Support custom SSH ports for the production and staging connection

2.2.0

• Fix compatibility problem with MariaDB and older MySQL versions
• New options PROD_DEPLOY_STRATEGY and STAG_DEPLOY_STRATEGY (conservative or risky)