Releases: EmbarkStudios/krates
Releases Β· EmbarkStudios/krates
0.18.1
Fixed
- PR#101 resolved #100 by correctly swallowing unknown fields for the various objects in a metadata dump.
0.18.0
Changed
- PR#99 updated to edition 2024.
- PR#99 changed from using
serde_derive
to manual deserialization.
Added
- PR#99 added support for serialization of metadata gated behind the
serialize
feature.
0.17.5
Fixed
- PR#98 resolved #84 and #97 by resolving
<crate>/<feature>
references to the correct crate in all cases, as it could have resolved to a crate with the same name but different version/feature set previously.
0.17.4
Fixed
- PR#96 fixed an issue where package specs didn't allow the
@
separator, resolving cargo-deny#717.
0.17.3
Fixed
- PR#94 fixed an issue with canonical path mismatches (I presume on Windows). Thanks @Tastaturtaste!
Added
- PR#95 added the 2024 variant so that edition 2024 (unstable) crates don't fail to be parsed from cargo-metadata. Thanks @kpcyrd!
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.