-
Notifications
You must be signed in to change notification settings - Fork 130
Release Process
Pre-release
-
Verify and test all PR(s) added since last release that are merged into
masterbranch. -
You may refer this PR for expected changes in version update https://github.com/rtCamp/nginx-helper/pull/226
-
Create a branch from latest
master, once all changes have been tested,git checkout -b release/x.x.x, replacex.x.xwith planned release version number. -
Update plugin version number in following locations.
- nginx-helper.php -
Version: x.x.x - readme.txt -
Stable tag: x.x.x - includes/class-nginx-helper.php - in class constructor
$this->version - README.md -
Stable tag: x.x.x
- nginx-helper.php -
-
Update the
Tested up tofield, in following locations, replacex.x.xwith the version of WordPress, the plugin was tested on.- README.md -
Tested up to: x.x.x - nginx-helper.php -
Tested up to: x.x.x - readme.txt -
Tested up to: x.x.x
- README.md -
-
Update Changelog and Upgrade Notice in
readme.txtandREADME.md -
Update Contributors list and add new contributors if any, in
readme.txtandREADME.md -
Update language file for translations, run this command from repo's root.
wp i18n make-pot . languages/nginx-helper.po
Release on WordPress.org
- Once version update PR is merged into
masterand a final test is done, follow below steps for releasing the plugin to WordPress.orggit checkout mastergit pull origin master-
git tag -a x.x.x -m "Tag Version x.x.x", replace x.x.x with planned release version -
git push origin x.x.x- This will trigger GitHub Action that will deploy tag contents to https://wordpress.org/plugins/nginx-helper
Post Release on WordPress.org
- Test the latest release.
- Once the release is updated on https://wordpress.org/plugins/nginx-helper, download the zip and store for next steps.
- Go to https://github.com/rtCamp/nginx-helper/tags, selected the pushed tag and
Create Release. - Add the Title and Description ( changelog ) of the release.
- Add downloaded zip to binaries section and Publish release.