yume/juniper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Release version 0.6.0

Browse source
This commit is contained in:
Magnus Hallin 2017-01-02 13:15:45 +01:00
parent 8f3e60a71c
commit f33213e17e
2 changed files with 5 additions and 3 deletions

2
Cargo.toml
View file

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

6
README.md
View file

@ -24,7 +24,7 @@ Add Juniper to your Cargo.toml:
```toml ```toml
[dependencies] [dependencies]
juniper = "0.5.3" juniper = "0.6.0"
``` ```
If you want the Iron integration enabled, you need to enable the `iron-handlers` If you want the Iron integration enabled, you need to enable the `iron-handlers`
@ -32,7 +32,7 @@ feature flag:
```toml ```toml
[dependencies] [dependencies]
juniper = { version = "0.5.3", features = ["iron-handlers"] } juniper = { version = "0.6.0", features = ["iron-handlers"] }
``` ```
## Building schemas ## Building schemas
@ -120,6 +120,8 @@ Juniper has not reached 1.0 yet, thus some API instability should be expected.
## 1.0 Roadmap ## 1.0 Roadmap
> Version 0.6.0 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 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 obvious dead-ends with respect to probable future features, and improving test
coverage for general execution. There are some chores that need to be completed coverage for general execution. There are some chores that need to be completed