Build & Release

Before deploy

1. Ensure the readme.txt and changelog.txt files have changelog entries for the changes included in the new version
2. Ensure the changelog date and version uses the following format: {year}.nn.nn {version}-dev.{number}. Sake expects to see and will replace 2020.nn.nn with the current version and {version}-dev.{number} with the version selected during deploy.
3. Ensure that the value for the Stable tag header in readme.txt is {version}-dev.{number}
4. Ensure that the value for the WC_Facebookcommerce::VERSION constant is {version}-dev.{number}
5. Ensure that the value for the Version header in facebook-for-woocommerce.php is {version}-dev.{number}
6. Ensure you have no untracked files or uncommitted changes on your working directory

Deploy

1. Set the WP_SVN_USER environment variable to the username that should be used to push changes to WordPress.org. Saké will ask for the password the first time that user attempts to commit.
2. Use npx sake deploy --deployAssets=0 to skip the shell:svn_commit_assets action not used on this repo

After deploy

If you deploy from a branch, before merging the changes into master, follow these steps to fix the tag that Sake creates:

1. git fetch to get the latest tags
2. git tag -d {version} to delete the tag that sake created
3. git tag {version} {hash of Facebook for WooCommerce versioning commit}
4. git push --tags -f to overwrite the tag on GitHub with the modified tag