Pushing a new version

When pushing a new version:

• Ensure README.md is up to date (are all the templates listed?).
• Rev the version in pubspec.yaml.
• Rev the corresponding version in lib/src/cli_app.dart.
• Make sure CHANGELOG.md is up-to-date.
• Commit to github.
• Sync locally: git checkout master; git pull
• Push to pub (pub publish; Devon or Seth can grant permission).
• Create a new GitHub release.
  • Go to https://github.com/google/stagehand/releases.
  • Click Draft a new release.
  • Set both the tag version and the release title to v1.X.Y (where 1.X.Y is the new version #).
  • Describe the release (just copy from CHANGELOG.md).
  • Click Publish release.

Version note: This package has been stable since 0.2.0. The 1.0.0 version is compatible with 0.2.0.

Notify authors

If any templates, template names, or template descriptions have changed, notify the authors of pages that depend on templates.

Update the website

If you added/removed a template or a template's name changed, update the website (http://stagehand.pub) and notify authors of other pages that depend on the list of templates. We generate the website from the metadata; text edits go in site/index.html.

After you've edited the website content, use grind to build the site (while in a non-gh-pages branch) and put it in your gh-pages branch:

git checkout master
dart tool/grind.dart update-gh-pages

After grind finishes, push your gh-pages branch to GitHub's gh-pages branch. http://stagehand.pub should update within seconds.

git checkout gh-pages
git push origin gh-pages