Skip to content
This repository has been archived by the owner on May 31, 2021. It is now read-only.

Pushing a new version

Kathy Walrath edited this page Mar 31, 2016 · 23 revisions

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 #).
    • Optionally, describe the release (but we usually don't; that's what the changelog is for).
    • Click Publish release.

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; 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.

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

Clone this wiki locally