Release 0.1.0

History.md

@@ -1,26 +1,32 @@
 
-0.0.5 / 2012-11-15 
+0.1.0 / 2012-11-20
+==================
+
+  * Add normalize command.
+  * Add update-dep command.
+
+0.0.5 / 2012-11-15
 ==================
 
   * Handle devDependencies.
 
-0.0.4 / 2012-11-12 
+0.0.4 / 2012-11-12
 ==================
 
   * Fix silly version reading bug.
 
-0.0.3 / 2012-11-11 
+0.0.3 / 2012-11-11
 ==================
 
   * Fix broken command line interface.
 
-0.0.2 / 2012-11-11 
+0.0.2 / 2012-11-11
 ==================
 
   * Improve readme.
   * Split analyze and install.
 
-0.0.1 / 2012-11-09 
+0.0.1 / 2012-11-09
 ==================
 
   * Initial version.

Readme.md

@@ -53,3 +53,13 @@ If different versions of the same lib are listed in two or more `package.json` f
 ## `rnpm analyze`
 
 When you run `rnpm analyze`, RNPM will check for conflicting dependency versions and warn you about them, without installing anything.
+
+## `rnpm update-dep`
+
+The `update-dep` command allows you to recursively update a dependency version across multiple `package.json` files. It accepts the following syntax:
+
+    $ rnpm update-dep <dependency> <version>
+
+## `rnpm normalize`
+
+The `normalize` command will check for conflicting dependency versions, and prompt you for the correct version on each inconsistency found. It's equivalent to calling `rnpm analyze` and then `rnpm update-dep` manually (but much faster).

package.json

@@ -6,7 +6,7 @@
     "npm",
     "package manager"
   ],
-  "version": "0.0.5",
+  "version": "0.1.0",
   "dependencies": {
     "commander": "~1.0.5",
     "dive": "~0.2.0",