Fix broken crate metadata, prepare 0.8.1 release

CHANGELOG.md

@@ -1,6 +1,10 @@
 Change log
 ==========
 
+## [0.8.1] – 2017-06-15
+
+Tiny release to fix broken crate metadata on crates.io.
+
 ## [0.8.0] – 2017-06-15
 
 ## Breaking changes
@@ -325,6 +329,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.8.0]: https://github.com/mhallin/juniper/compare/0.8.0...0.8.1
 [0.8.0]: https://github.com/mhallin/juniper/compare/0.7.0...0.8.0
 [0.7.0]: 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

Cargo.toml

@@ -1,13 +1,13 @@
 [package]
 name = "juniper"
-version = "0.8.0"
+version = "0.8.1"
 authors = ["Magnus Hallin <[email protected]>"]
 description = "GraphQL server library"
 license = "BSD-2-Clause"
-documentation = "http://mhallin.github.io/juniper"
-repository = "https://docs.rs/juniper"
+documentation = "https://docs.rs/juniper/0.8.1/juniper/"
+repository = "https://github.com/mhallin/juniper"
 readme = "README.md"
-keywords = ["graphql", "server", "iron", "http", "web"]
+keywords = ["graphql", "server", "iron", "web", "rocket"]
 categories = ["web-programming"]
 
 [package.metadata.docs.rs]

README.md

@@ -24,23 +24,23 @@ Add Juniper to your Cargo.toml:
 
 ```toml
 [dependencies]
-juniper = "0.8.0"
+juniper = "0.8.1"
 ```
 
 If you want the Iron integration enabled, you need to enable the `iron-handlers`
 feature flag:
 
 ```toml
 [dependencies]
-juniper = { version = "0.8.0", features = ["iron-handlers"] }
+juniper = { version = "0.8.1", features = ["iron-handlers"] }
 ```
 
 If you want the Rocket integration enabled, you need to use the nightly Rust
 compiler and enable the `rocket-handlers` feature flag:
 
 ```toml
 [dependencies]
-juniper = { version = "0.8.0", features = ["rocket-handlers"] }
+juniper = { version = "0.8.1", features = ["rocket-handlers"] }
 ```
 
 ## Building schemas
@@ -128,7 +128,7 @@ Juniper has not reached 1.0 yet, thus some API instability should be expected.
 
 ## 1.0 Roadmap
 
-> Version 0.8.0 probably be re-released as 1.0 to indicate API stability.
+> Version 0.8.1 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
@@ -149,7 +149,7 @@ as well.
 * [X] Investigate asynchronous execution - implementing it is not necessary, but
   at least look at what API changes will be needed for us to hook into
   [Tokio][tokio], for example.
-* [ ] Larger examples to illustrate things like database access
+* [X] Larger examples to illustrate things like database access
 
 [graphql]: http://graphql.org
 [iron]: http://ironframework.io