Fix issue with executing cargo-metadata (#68)

* Stop supplying manifest-path
* Prepare release 0.5.1

CHANGELOG.md

@@ -6,6 +6,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.1] - 2019-12-19
+### Fixed
+- Fixed issue where both `--manifest-path` and working directory were set when executing `cargo-metadata`, causing it to fail if a executed in a subdirectory.
+
 ## [0.5.0] - 2019-12-18
 ### Added
 - Added the `advisories` check and configuration section for checking crates against an advisory database to detect security vulnerabilities, unmaintained crates, and crates with security notices

Cargo.toml

@@ -2,7 +2,7 @@
 name = "cargo-deny"
 description = "Cargo plugin to help you manage large dependency graphs"
 repository = "https://github.com/EmbarkStudios/cargo-deny"
-version = "0.5.0"
+version = "0.5.1"
 authors = ["Embark <[email protected]>", "Jake Shadle <[email protected]>"]
 edition = "2018"
 license = "MIT OR Apache-2.0"

src/lib.rs

@@ -400,9 +400,9 @@ impl AsRef<[KrateDetails]> for Krates {
 }
 
 pub fn get_all_crates<P: AsRef<Path>>(root: P) -> Result<Krates, Error> {
-    let cargo_toml = root.as_ref().join("Cargo.toml");
+    //let cargo_toml = root.as_ref().join("Cargo.toml");
     let metadata = cargo_metadata::MetadataCommand::new()
-        .manifest_path(cargo_toml)
+        //.manifest_path(cargo_toml)
         // We run cargo_metadata from the root path provided by the user
         // so that any potential .cargo/config is picked up correctly,
         // as eg. adding registries in the config that are used by one