Releases: EmbarkStudios/krates
Releases Β· EmbarkStudios/krates
0.17.0
Added
- PR#90 added
Krates::resolved_dependency
to get the Krate
(if any) that was resolved for a Package
's Dependency
.
Fixed
- PR#86 and PR#87 resolved #85 caused by the stable package format URL-encoding query parameters, unlike the old opaque format, causing
krates
to be unable to resolve dependencies to the appropriate crate node.
Changed
- PR#90 made
cargo_metadata
optional, if not selected types internal to this crate are used (and exported) instead. The types are currently mostly the same, but this might change in the future.
0.16.10
Fixed
- PR#83 resolved #82 by properly handling
cfg()
specific dependencies for the same crate with different features enabled.
- PR#83 fixed an issue where
cfg(any())
crates would be pulled into the graph erroneously if not performing target filtering.
0.16.9
Fixed
- PR#81 re-resolved #79 because the PR#80 completely broke in the presence of cargo patches.
0.16.8
Fixed
- PR#80 resolved #79 by fixing an extreme edge case with dependency renaming.
0.16.7
Fixed
- PR#78 fixed an issue where setting manifest_path to
Cargo.toml
without preceding ./
would cause the current directory be set to empty, and cargo_metadata to fail.
Release 0.16.6
Fixed
- PR#77 resolved #76 by special casing "wildcard" version requirements if the version being tested is a pre-release, as pre-releases must have at least one comparator.
Release 0.16.5
Fixed
- PR#75 resolved #74 by just always checking version requirements for dependencies. Sigh.
Release 0.16.4
Fixed
- PR#73 resolved #72 by correctly parsing the new stable package ids where a specifier was not used.