Release on npm as the last step

FagnerMartinsBrack · FagnerMartinsBrack · commit 76932e33d9b4 · 2015-06-27T13:55:37.000-03:00
IF we do this, then the "view documentation for the latest release" link
in the README shows on npm the current version instead of the previous.

That link is not even needed on npm. We just keep it there because there
is no procedure to remove it when a new version is released.
diff --git a/README.md b/README.md
@@ -241,9 +241,9 @@ Check out the [Contributing Guidelines](CONTRIBUTING.md)
 * Commit with the message "Release version x.x.x"
 * Create version tag in git
 * Create a github release and upload the minified file
-* Release on npm
 * Link the documentation of the latest release tag in the `README.md`
 * Commit with the message "Prepare for the next development iteration"
+* Release on npm
 
 ## Authors
 
