Bump README to 0.10.4.

README.md

@@ -43,18 +43,18 @@ your own SBT project:
 resolvers += Resolver.sonatypeRepo("releases")
 
 // use this if you just want jawn's parser, and will implement your own facade
-libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.10.3"
+libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.10.4"
 
 // use this if you want jawn's parser and also jawn's ast
-libraryDependencies += "org.spire-math" %% "jawn-ast" % "0.10.3"
+libraryDependencies += "org.spire-math" %% "jawn-ast" % "0.10.4"
 ```
 
 If you want to use Jawn's parser with another project's AST, see the
 "Supporting external ASTs with Jawn" section. For example, with Spray
 you would say:
 
 ```scala
-libraryDependencies += "org.spire-math" %% "jawn-spray" % "0.10.3"
+libraryDependencies += "org.spire-math" %% "jawn-spray" % "0.10.4"
 ```
 
 There are a few reasons you might want to do this:
@@ -165,7 +165,7 @@ This is how you would include the subproject in build.sbt:
 ```scala
 resolvers += Resolver.sonatypeRepo("releases")
 
-libraryDependencies += "org.spire-math" %% jawn-"XYZ" % "0.10.3"
+libraryDependencies += "org.spire-math" %% jawn-"XYZ" % "0.10.4"
 ```
 
 This is an example of how you might use the parser into your code:
@@ -189,7 +189,7 @@ snippet to your `build.sbt` file:
 ```scala
 resolvers += Resolver.sonatypeRepo("releases")
 
-libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.10.3"
+libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.10.4"
 ```
 
 To support your AST of choice, you'll want to define a `Facade[J]`