rev to 0.2.3

[devoncarew]

fix #36

@sethladd, can you land this and push a new version of the plugin?

[sethladd]

Let's land #42 and then we'll publish.

[devoncarew]

Reverted the package.json changes; landing.

[radicaled]

apm publish handles tagging versions; maybe you should rely on that when you're ready to launch?

apm publish {major|minor|patch}

[devoncarew]

Yup, Seth let me know I shouldn't be manually reving the package version. Would like to figure out some system for keeping the pubspec and changelog versions in sync.

[radicaled]

We have grindr, maybe copy the apm flow:

dart tool/grind.dart publish $version
==> dirty check, explode if tree is dirty
==> make sure synced with master, explode if not
==> parse package.json, get $parsedVersion
==> increment $parsedVersion => $newVersion, update pubspec.yaml, update package.json
==> updates CHANGELOG.md, replaces "# Upcoming Version" ==> "# $newVersion"
==> git commit -a -m "foo bar"
==> git tag $newVersion
==> git push -t
==> apm publish -t $version