Releasing a new version

Make sure to check off the following list when releasing a new version:

• Open composer.json and ensure that the felixarntz/plugin-lib dependency is set to its latest stable version. It must not use dev-master.
• Run composer update and npm update, just to ensure none of the dependencies are out of date.
• Add a changelog section for the new version in readme.txt. Follow the patterns of the existing changelog sections, using prefixes like "Added:", "Enhanced:", "Tweaked:" and "Fixed:" to describe every change accordingly. Sort the changelog entries in that way.
• Change the version field in composer.json to the new version number.
• Change the version field in package.json to the new version number.
• Change the $version property in src/torro-forms.php to the new version number (part of the Torro_Forms::load_base_properties() method).
• Run gulp build.
• Commit the changes to git with message like "Version bump to {version}." (replace "{version}" with the new version number).
• Push the changes to GitHub.
• Do not commit anything else at this point, until the release is done.
• Wait for the Travis build to be finished to ensure all tests pass.
• Run sh ./deploy.sh {SVNUSER} {SVNPASS} (with your wordpress.org username and password) to create a new tag on GitHub and push that out to wordpress.org as well. The script will take care of everything required for the plugin repository. When asked, confirm the pre-written commit message.
• On GitHub, create a new release from the tag created by the script. Use the version number as release title and the list of changelog entries as release description.

That's it - you just created a new release of Torro Forms! Please make sure to test-download it from wordpress.org and activate it, just to ensure no build errors occurred. If that's confirmed, you're ready to share it with the world.