deps: update ureq to 2.5.0

Author: noib3

Cargo.toml

@@ -22,8 +22,7 @@ bitcoin_hashes = "0.11"
 tar = "0.4"
 zip = "0.5"
 
-# allows to keep MSRV 1.41.1
-ureq = "1.0"  
+ureq = "2.5.0"
 filetime = "=0.2.15"
 flate2 = "=1.0.22"
 

README.md

@@ -17,7 +17,7 @@ assert_eq!(0, bitcoind.client.get_blockchain_info().unwrap().blocks);
 When a feature like `22_0` is selected, the build script will automatically download the bitcoin core version `22.0`, verify the hashes and place it in the build directory for this crate.
 Use utility function `downloaded_exe_path()` to get the downloaded executable path.
 
-### Example 
+### Example
 
 In your project Cargo.toml, activate the following features
 
@@ -35,7 +35,7 @@ let bitcoind = bitcoind::BitcoinD::new(bitcoind::downloaded_exe_path().unwrap())
 
 ## MSRV
 
-1.41.1
+1.53
 
 ## Issues with traditional approach
 
@@ -50,7 +50,7 @@ I used integration testing based on external bash script launching needed extern
 
   * It waits until bitcoind daemon become ready to accept RPC commands
   * bitcoind use a temporary directory as datadir. You can specify the root of your temp directories so that you have node's datadir in a RAM disk (eg `/dev/shm`)
-  * Free ports are asked to the OS (a low probability race condition is still possible) 
+  * Free ports are asked to the OS (a low probability race condition is still possible)
   * the process is killed when the struct goes out of scope no matter how the test finishes
   * allows easy spawning of dependent process like https://github.com/RCasatta/electrsd
 

build.rs

@@ -103,7 +103,7 @@ fn main() {
         );
         println!("url:{}", url);
         let mut downloaded_bytes = Vec::new();
-        let resp = ureq::get(&url).call();
+        let resp = ureq::get(&url).call().unwrap();
         assert_eq!(resp.status(), 200, "url {} didn't return 200", url);
 
         let _size = resp