Skip to content

Releases: EmbarkStudios/krates

0.20.0

22 May 13:36

Choose a tag to compare

Changed

0.19.0

03 Apr 14:34

Choose a tag to compare

Changed

0.18.1

27 Feb 06:58

Choose a tag to compare

Fixed

  • PR#101 resolved #100 by correctly swallowing unknown fields for the various objects in a metadata dump.

0.18.0

24 Feb 07:41

Choose a tag to compare

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

14 Nov 15:02

Choose a tag to compare

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

14 Nov 12:29

Choose a tag to compare

Fixed

  • PR#96 fixed an issue where package specs didn't allow the @ separator, resolving cargo-deny#717.

0.17.3

11 Nov 14:40

Choose a tag to compare

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.2

20 Sep 08:40

Choose a tag to compare

Changed

0.17.1

02 Aug 11:55

Choose a tag to compare

Changed

0.17.0

26 Jun 21:55

Choose a tag to compare

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.