Skip to content

Commit f33213e

Browse files
committed
Release version 0.6.0
1 parent 8f3e60a commit f33213e

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "juniper"
3-
version = "0.5.3"
3+
version = "0.6.0"
44
authors = ["Magnus Hallin <[email protected]>"]
55
description = "GraphQL server library"
66
license = "BSD-2-Clause"

README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,15 +24,15 @@ Add Juniper to your Cargo.toml:
2424

2525
```toml
2626
[dependencies]
27-
juniper = "0.5.3"
27+
juniper = "0.6.0"
2828
```
2929

3030
If you want the Iron integration enabled, you need to enable the `iron-handlers`
3131
feature flag:
3232

3333
```toml
3434
[dependencies]
35-
juniper = { version = "0.5.3", features = ["iron-handlers"] }
35+
juniper = { version = "0.6.0", features = ["iron-handlers"] }
3636
```
3737

3838
## Building schemas
@@ -120,6 +120,8 @@ Juniper has not reached 1.0 yet, thus some API instability should be expected.
120120

121121
## 1.0 Roadmap
122122

123+
> Version 0.6.0 will probably be re-released as 1.0 to indicate API stability.
124+
123125
The road to 1.0 _focuses_ on two aspects: making sure the API hasn't got any
124126
obvious dead-ends with respect to probable future features, and improving test
125127
coverage for general execution. There are some chores that need to be completed

0 commit comments

Comments
 (0)