Deps. bump.

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "exifmv"
-version = "0.2.0"
+version = "0.2.1"
 authors = ["Moritz Moeller <[email protected]>"]
 edition = "2021"
 license = "Apache-2.0 OR BSD-3-Clause OR MIT OR Zlib"
@@ -20,11 +20,11 @@ name = "exifmv"
 path = "src/main.rs"
 
 [dependencies]
-chrono = "0.4.24"
-clap = "3.2.23"
+chrono = "0.4.28"
+clap = "3.2.25"
 error-chain = "0.12.4"
 kamadak-exif = "0.5.5"
-trash = "3.0.1"
+trash = "3.0.6"
 walkdir = "2.3.3"
 
 [profile.release]

README.md

@@ -40,10 +40,11 @@ location on most operating systems.
 Before doing any deletion or moving-to-trash `exifmv` checks that the file
 size matches. This is not the same as checking the files byte-by-byte. But
 due to almost all image file formats using some kind of compression matching
-size is a good enough indicator for files being identical for this application
+size is a good enough indicator for files being identical for this
+application.
 
 All that being said: I have been using this app since about seven years
-without loosing any images. As such I have quite a lot of _empirical_
+without loosing any images. As such I have quite a lot of *empirical*
 evidence that it doesn’t destroy data.
 
 Still – writing some proper tests would likely give everyone else more