Prepare for 0.6.1 release

CHANGELOG.md

@@ -1,7 +1,28 @@
 Change log
 ==========
 
-## 0.6.0 – Unreleased
+## [0.6.1] – 2017-01-06
+
+### New features
+
+* Optional Serde support (#8)
+
+### Improvements
+
+* The `graphql_input_object!` macro can now be used to define input
+  objects as public Rust structs.
+* GraphiQL in the Iron GraphiQL handler has been updated to 0.8.1
+  (#11)
+
+### Minor breaking changes
+
+Some undocumented but public APIs were changed.
+
+* `to_snake_case` correctly renamed to `to_camel_case` (#9)
+* JSON serialization of `GraphQLError` changed to be more consistent
+  with how other values were serialized (#10).
+
+## [0.6.0] – 2017-01-02
 
 TL;DR: Many big changes in how context types work and how they
 interact with the executor. Not too much to worry about if you're only
@@ -216,4 +237,6 @@ using the macros and not deriving `GraphQLType` directly.
   cases of the macros have gotten tests to verify their correctness.
 
 
+[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
 [0.5.3]: https://github.com/mhallin/juniper/compare/0.5.2...0.5.3

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "juniper"
-version = "0.6.0"
+version = "0.6.1"
 authors = ["Magnus Hallin <[email protected]>"]
 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.0"
+juniper = "0.6.1"
 ```
 
 If you want the Iron integration enabled, you need to enable the `iron-handlers`
 feature flag:
 
 ```toml
 [dependencies]
-juniper = { version = "0.6.0", features = ["iron-handlers"] }
+juniper = { version = "0.6.1", 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.0 will probably be re-released as 1.0 to indicate API stability.
+> Version 0.6.1 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