Pushing a new version

When pushing a new version:

• Ensure README is up to date (are all the templates listed?)
• rev the version in the pubspec.yaml file
• rev the corresponding version in lib/src/cli_app.dart
• make sure the changelog.md file is up-to-date
• commit
• create a new github release (https://github.com/google/stagehand/releases)
• push to pub (Devon or Seth can grant permission).
• possibly, rev the version to the next highest number, with the -dev suffix

If you added/removed a template or a template's name changed, update the website (http://stagehand.pub). We generate the website from the metadata, using grind to rebuild it and copy it over to the gh-pages branch, where its served from: grind update-gh-pages.

A note about version numbers:

• Increment/add +X (0.2.6+X) for minor bug fixes and updates.
• Increment the 3rd number (0.2.X) for something new and fresh — a major change to a sample, or a refresh of all the samples.
• Increment the 2nd number (0.X.0) for a major or incompatible tooling API change. This should be rare. An example would be if we added the ability to get plugins.
• It's a little strange that it's all < 1.0.0, but oh well.