Prepare for 0.7.0 release

CHANGELOG.md

@@ -1,6 +1,21 @@
 Change log
 ==========
 
+## [0.7.0] – 2017-02-26
+
+### Breaking changes
+
+* The `iron-handlers` feature now depends on Iron 0.5
+  ([#30](https://github.com/mhallin/juniper/pull/30)). Because of
+  this, support for Rust 1.12 has been dropped. It might still work if
+  you're not using the Iron integrations feature, however.
+
+### New features
+
+* Input objects defined by the `graphql_input_object!` can now be used
+  as default values to field arguments and other input object fields.
+
+
 ## [0.6.3] – 2017-02-19
 
 ### New features
@@ -278,6 +293,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.3...0.7.0
 [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

Cargo.toml

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

README.md

@@ -24,15 +24,15 @@ Add Juniper to your Cargo.toml:
 
 ```toml
 [dependencies]
-juniper = "0.6.3"
+juniper = "0.7.0"
 ```
 
 If you want the Iron integration enabled, you need to enable the `iron-handlers`
 feature flag:
 
 ```toml
 [dependencies]
-juniper = { version = "0.6.3", features = ["iron-handlers"] }
+juniper = { version = "0.7.0", 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.3 will probably be re-released as 1.0 to indicate API stability.
+> Version 0.7.0 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