v3.1.1

Patch Changes

• Prevent plugin and theme conflicts from adversely affecting cache clear #29

v3.1.0

Minor Changes

• Copy post-deploy SCRIPT to the remote if it exists in the repo but not on the remote. This allows for storing script files outside of SRC_PATH. #12

Patch Changes

• Fix action failures caused by attempts to rsync wpe-cache-plugin #8

v3.0

Release Notes: Newly enhanced WP Engine Github Action.
Key updates:

• branch management: This is now managed by the Github Actions branches: operator instead of within the Action itself. This will lend to more flexibility to execute different workflows for different branches.
• Post Deploy Script: the SCRIPT: variable can now be used to call and execute a bash script after the deploy is made to the server.
• Multi-step support: Now a single branch can be used to run a multistep job. Ex. deploying main branch to staging, running tests other actions, then running the WPE action to deploy the compiled artifacts to production.
• SSH connectivity enhancement for more reliable interaction with the SSH Gateway

v2.3.5

bugfix: file permissions for SRC_PATH are set to WP Engine platform defaults. 775 for dir and 664 for files.
For more detail on WP Engine File permissions, please refer to our documentation here.

v2.3.3

Bugfix - now users can deploy just STG and DEV variables without a PRD_BRANCH or PRD_ENV in case they would like to work on pre-production alone before connecting production branch or sites.

backend visibility enhancement

v2.3.2

Removed changelog from Readme and created link.

v2.3.1

V2.3.1 NOW AVAILABLE!

Changelog: v.2.3.1 Restricted paths are excluded from the rsync deploy such as wp-config.php as well as platform specific files that customers do not have permissions to edit. No action required. Most of these paths are already configured in the WP Engine sample gitignore so conflicts should be minimal. This is primarily to prevent a --delete flag from completely deleting WPE platform files or a customers wp-content/uploads/ since neither of these are commonly included in a git repo.

This should enhance expected behavior of the toolkit for users. Inspect exclude.txt for reference.

v2.3

Adding CACHE_CLEAR option to the toolkit to disable cache clearing on deploy.

Minor optimizations will be v2.3.* moving forward.
The toolkit now has all vars and options we intentionally set out to build into the tool. Any further suggestions are welcome. Create an issue or pull request.

v2.2

v2.2
Feature fix for v2.1

• This will REQUIRE users to update their main.yml file to use with: instead of env: if the latest version of the repo is being called by wpengine/github-action-wpe-site-deploy@main.
• This fixes known bugs in the v2.1 deploy to fully enable users to specify FLAGS and also have a default rsync for historical users if not FLAG var is set.
• Samplemain.yml is updated with latest syntax and version example for best practice.
• This also enables easier variable additions in future releases with no impact to customers configs.

v2.1

DO NOT USE - Deploy FLAGS are now available. Customers can now specify any rsync flags they would like, such as --delete to remove extra files not versioned in their repo. The action will default to a non-destructive sync unless specified in the main.yml.

Known bugs: If FLAGS are not set, rsync with not recursively sync files all files. This will be fixed in v2.2.