Prepare for 0.6.3 release

CHANGELOG.md

@@ -1,6 +1,13 @@
 Change log
 ==========
 
+## [0.6.3] – 2017-02-19
+
+### New features
+
+* Add support for default values on input object fields
+  ([#28](https://github.com/mhallin/juniper/issues/28))
+
 ## [0.6.2] – 2017-02-05
 
 ### New features
@@ -271,6 +278,7 @@ using the macros and not deriving `GraphQLType` directly.
 * Macro syntax stability has also been improved. All syntactical edge
   cases of the macros have gotten tests to verify their correctness.
 
+[0.6.3]: https://github.com/mhallin/juniper/compare/0.6.2...0.6.3
 [0.6.2]: https://github.com/mhallin/juniper/compare/0.6.1...0.6.2
 [0.6.1]: https://github.com/mhallin/juniper/compare/0.6.0...0.6.1
 [0.6.0]: https://github.com/mhallin/juniper/compare/0.5.3...0.6.0

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "juniper"
-version = "0.6.2"
+version = "0.6.3"
 authors = ["Magnus Hallin <mhallin@fastmail.com>"]
 description = "GraphQL server library"
 license = "BSD-2-Clause"

README.md

@@ -24,7 +24,7 @@ Add Juniper to your Cargo.toml:
 
 ```toml
 [dependencies]
-juniper = "0.6.2"
+juniper = "0.6.3"
 ```
 
 If you want the Iron integration enabled, you need to enable the `iron-handlers`
@@ -32,7 +32,7 @@ feature flag:
 
 ```toml
 [dependencies]
-juniper = { version = "0.6.2", features = ["iron-handlers"] }
+juniper = { version = "0.6.3", features = ["iron-handlers"] }
 ```
 
 ## Building schemas
@@ -120,7 +120,7 @@ Juniper has not reached 1.0 yet, thus some API instability should be expected.
 
 ## 1.0 Roadmap
 
-> Version 0.6.2 will probably be re-released as 1.0 to indicate API stability.
+> Version 0.6.3 will probably be re-released as 1.0 to indicate API stability.
 
 The road to 1.0 _focuses_ on two aspects: making sure the API hasn't got any
 obvious dead-ends with respect to probable future features, and improving test