Enable bitcoin_hashes v0.14.0

Hardware devices like the smallest binary possible, currently if one
builds with `rust-bitcoin v0.32` and `rust-bip39` they get two versions
of `bitcoin_hashes` in the dependency graph because we don't support
`bitcoin_hashes v0.14`.

Note that using `bitcoin_hashes 0.14` bumps the MSRV to Rust v1.56.1

Author: tcharding

Cargo.toml

@@ -49,13 +49,13 @@ serde = { version = "1.0", default-features = false, features = [ "alloc" ], opt
 zeroize = { version = "1.5", features = ["zeroize_derive"], optional = true }
 
 # Unexported dependnecies
-bitcoin_hashes = { version = ">=0.12, <=0.13", default-features = false }
+bitcoin_hashes = { version = ">=0.12,<0.15", default-features = false }
 unicode-normalization = { version = "0.1.22", default-features = false, optional = true }
 
 [dev-dependencies]
 # Enabling the "rand" feature by default to run the benches
 bip39 = { path = ".", features = ["rand"] }
-bitcoin_hashes = ">=0.12,<0.14" # enable default features for test
+bitcoin_hashes = ">=0.12,<0.15" # enable default features for test
 
 
 [package.metadata.docs.rs]

README.md

@@ -35,9 +35,10 @@ The `bitcoin_hashes` range dependency effects the MSRV as follows
 
 - `bitcoin_hashes v0.12`: MSRV v1.41.1
 - `bitcoin_hashes v0.13`: MSRV v1.48.0
+- `bitcoin_hashes v0.14`: MSRV v1.56.0
 
 When using older version of Rust, you might have to pin the versions of several crates, for an up-to-date list refer to [`contrib/test.sh`](contrib/test.sh):
-
+ 
 ```bash
 cargo update --package "bitcoin_hashes" --precise "0.12.0"
 cargo update --package "rand" --precise "0.6.0"

pins.sh

@@ -0,0 +1,7 @@
+#!/bin/bash
+
+cargo update --package "syn" --precise "1.0.109"
+# cargo update --package "zeroize" --precise "1.5.7"
+# cargo update --package "rand_isaac" --precise "0.1.0"
+# cargo update --package "rand" --precise "0.6.0"
+# cargo update --package "semver" --precise "0.8.0"