[bitreq] Bump crate version to 0.3

I believe we should go ahead and release bitreq 0.3 with all the
changes we made to it, as its a substantial improvement for async
clients and now something that could reasonably be used in place of
`reqwest` in most cases.

There's some remaining proxy issues, but those can be resolved in a
point release without API change.

Author: TheBlueMatt

bitreq/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "bitreq"
-version = "0.2.0"
+version = "0.3.0"
 authors = ["Jens Pitkanen <[email protected]>", "Tobin C. Harding <[email protected]>"]
 description = "Simple, minimal-dependency HTTP client"
 documentation = "https://docs.rs/bitreq"

jsonrpc/Cargo.toml

@@ -34,7 +34,7 @@ serde = { version = "1", features = ["derive"] }
 serde_json = { version = "1", features = [ "raw_value" ] }
 
 base64 = { version = "0.22.1", optional = true }
-bitreq = { version = "0.2.0", path = "../bitreq", features = ["json-using-serde"], optional = true }
+bitreq = { version = "0.3.0", path = "../bitreq", features = ["json-using-serde"], optional = true }
 socks = { version = "0.3.4", optional = true}
 
 [lints.rust]

node/Cargo.toml

@@ -27,7 +27,7 @@ env_logger = { version = "0.9.3", default-features = false }
 anyhow = { version = "1.0.66", optional = true }
 bitcoin_hashes = { version = ">= 0.13, <= 0.14", optional = true }
 flate2 = { version = "1.0", optional = true }
-bitreq = { version = "0.2.0", path = "../bitreq", features = ["https"], optional = true }
+bitreq = { version = "0.3.0", path = "../bitreq", features = ["https"], optional = true }
 tar = { version = "0.4", optional = true }
 zip = { version = "0.6.6", default-features = false, features = ["bzip2", "deflate"], optional = true }