diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3f9a3e65..0ba47c97 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,4 @@
-## Unreleased
+## 0.5.0
 
 ### Potential Breaking Changes
 
diff --git a/Cargo.toml b/Cargo.toml
index 194eaf2b..5a70f1e2 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "proptest"
-version = "0.4.2"
+version = "0.5.0"
 authors = ["Jason Lingle"]
 license = "MIT/Apache-2.0"
 readme = "README.md"
diff --git a/README.md b/README.md
index a34ddd76..45f24436 100644
--- a/README.md
+++ b/README.md
@@ -84,7 +84,7 @@ In `Cargo.toml`, add
 
 ```toml
 [dev-dependencies]
-proptest = "0.4.2"
+proptest = "0.5.0"
 ```
 
 and at the top of `main.rs` or `lib.rs`:
@@ -366,11 +366,6 @@ shrinking based on the output value, whereas Proptest must hold on to all
 the intermediate states and relationships in order for its richer shrinking
 model to work.
 
-- In cases where one usually does have a single canonical way to generate
-values per type, Proptest will be more verbose than QuickCheck since one
-needs to name the strategy every time rather than getting them implicitly
-based on types.
-
 ## Limitations of Property Testing
 
 Given infinite time, property testing will eventually explore the whole
@@ -385,7 +380,7 @@ use proptest::prelude::*;
 
 proptest! {
     #[test]
-    fn i64_abs_is_never_negative(a in prop::num::i64::ANY) {
+    fn i64_abs_is_never_negative(a in any::<i64>()) {
         assert!(a.abs() >= 0);
     }
 }
diff --git a/src/lib.rs b/src/lib.rs
index 72fc33d1..bc4b8e00 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -95,7 +95,7 @@
 //!
 //! ```toml
 //! [dev-dependencies]
-//! proptest = "0.4.2"
+//! proptest = "0.5.0"
 //! ```
 //!
 //! and at the top of `main.rs` or `lib.rs`: