crates.io · #2487 most downloaded on crates.io

guppy

0.19.117M downloads/moguppy-rs/guppy ↗New releases in your daily digest, changelog included.

Track and query Cargo dependency graphs.

Last release 14 days ago
24 Sep 2026
Ships fairly regularly
a new release about every 6 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
7 years old
78 releases · first in 2019

Release timeline

78 releases since 2019

20192020202120222023202420252026

Releases

0.19.124 Sept 20262 sources agree
custom-platforms : Add support for custom platforms specified as JSON.
Added

New features:

custom-platforms: Add support for custom platforms specified as JSON.

custom-cfg-platforms: Add support for custom platforms specified as rustc --print=cfg output.

These features forward to target-spec's custom and custom-cfg features, respectively.

Thanks UebelAndre for your contribution!
Open source →
0.19.019 Sept 20262 sources agree
ConditionalLink::declarations , which returns a new LinkDeclarations enum: whether the link's platform statuses were derived from every declaration of
Added

ConditionalLink::declarations, which returns a new LinkDeclarations
enum: whether the link's platform statuses were derived from every
declaration of the dependency (Unsplit), only the ones without
optional = true (Required), or only the ones with it (Optional).
LinkDeclarations::includes_required and includes_optional answer whether
a link covers a given kind of declaration.

Changed

ConditionalLink::package_link is replaced by package_links, an iterator
over every PackageLink the conditional link was derived from. This is
usually one link, but one dependency name can resolve to several packages,
either through a package = "..." rename or through different versions of
one package declared for different targets. For example, consider this
Cargo.toml:

[package] name = "main" [dependencies] serde = { package = "serde_core", version = "1", optional = true } [target.'cfg(any())'.dependencies] serde = { version = "1", optional = true } [features] serde = ["dep:serde", "serde/std"]

The package graph has two links out of main, main -> serde_core and
main -> serde, both with the dependency name serde. The feature serde
produces three conditional links:

main/serde -> main/dep:serde, from dep:serde. This activates the
dependency name, so package_links returns both main -> serde_core and
main -> serde.

main/serde -> serde_core/std, from serde/std. package_links returns
only main -> serde_core.

main/serde -> serde/std, also from serde/std. package_links returns
only main -> serde.

FeatureQuery::resolve_with and resolve_with_fn now visit a weak dependency
feature (dep?/feature) once for each kind of declaration of dep, not once
for the whole edge. Consider:

[dependencies] foo = { version = "1" } [build-dependencies] foo = { version = "1", optional = true } [features] weak = ["foo?/std"]

The visitor sees weak -> foo/std as a Required link covering
[dependencies]. If dep:foo is activated, it sees the same endpoints again
as an Optional link covering [build-dependencies]. The edge is followed if
the visitor accepts either link. Use ConditionalLink::declarations to tell
the two apart. FeatureSet::conditional_links is unchanged: it returns one
Unsplit link for the edge.

This is part of the fix to weak dependency features described below.

Fixed

Features that refer to a dependency name shared by several packages now take
all of those packages into account (#682).

One dependency name can resolve to several packages, either through a
package = "..." rename or through different versions of one package
declared for different targets. For example, semver 1.0.28 does something
like this:

[dependencies] serde = { version = "1", package = "serde_core", optional = true } [target.'cfg(any())'.dependencies] serde = { version = "1", optional = true } [features] serde = ["dep:serde"]

The name serde resolves to both serde_core and serde. Previously, the
feature graph kept only one of the packages under each name. For semver,
that was serde, which cfg(any()) never builds, so enabling the serde
feature left serde_core out of guppy's feature resolution, and therefore
out of CargoSet results.

Now, matching Cargo:

dep:serde is activated wherever any declaration of serde applies.

serde/feature turns on feature in each package, under that package's
own platform conditions. It also activates dep:serde wherever an
optional declaration of any of the packages applies.

serde?/feature turns on feature in each package that is otherwise
activated, again under that package's own platform conditions.

As a result, if only some of the packages under a name have a feature that
name/feature or name?/feature refers to, the feature graph now reports a
missing-feature warning for the others. (Cargo itself rejects such a
manifest, so this only happens with metadata that didn't come from Cargo.)

Thanks UebelAndre for your first
contribution!

With the version 2 and 3 feature resolvers, an optional build dependency
activated only through its own package's features was never built (#699):

[build-dependencies] cc = { version = "1", optional = true } [features] bundled = ["dep:cc"]

Enabling bundled now builds cc on the host, as Cargo does. cc/feature
entries and the version 1 resolver were not affected.

Fixed a number of more contrived cases in guppy's simulation of Cargo's
feature resolution:

Several bugs with weak dependency features (dep?/feature). guppy tracked
whether dep was activated at all, whereas Cargo resolves each declaration
of dep on its own. Consider:

[dependencies] foo = { version = "1" } bar = { version = "1", optional = true } [build-dependencies] foo = { version = "1", optional = true } bar = { version = "1" } helper = { version = "1" } # helper depends on foo itself [features] weak = ["foo?/std", "bar?/std"]

Previously, enabling weak:

activated dep:foo, so foo was also built on the host. It no longer
does, and the feature graph no longer has an edge from weak to
dep:foo. A dependency required on one platform and optional on another
had dep:foo added the same way.

enabled std on the foo that helper builds on the host, even though
nothing had activated foo's optional build declaration. Now only the foo
built on the target gets std.

activated dep:bar in the same way, so bar was also built on the
target. Now bar only gets std on the host, where it is required, and
is not built on the target.

Of these, the second did not affect the version 1 resolver, which unifies
features across the host and the target.

As part of this fix, FeatureQuery::resolve_with and resolve_with_fn
visit a weak dependency feature once for each kind of declaration. See the
entry under "Changed" above.

Reverse feature queries with FeatureQuery::resolve_with or
resolve_with_fn could leave out weak dependency features, depending on
which features the query started from. For example, regex-automata has:

[dependencies] aho-corasick = { version = "1", optional = true } [features] logging = ["aho-corasick?/logging"]

A reverse query from aho-corasick/logging did not return
regex-automata/logging.

Reverse queries now offer both links of a weak dependency feature as soon as
it is reached. With a visitor that accepts every link, a reverse query
returns the same set as FeatureQuery::resolve. Forward queries are
unchanged.

A foo/std entry could also turn on a feature named foo in the same
package, in cases where Cargo doesn't. For example:

[package] name = "main" [dependencies] bar = { version = "1" } [target.'cfg(unix)'.dependencies] foo = { version = "1" } [target.'cfg(windows)'.dependencies] foo = { version = "1", optional = true } [features] foo-std = ["foo/std"] bar = [] bar-std = ["bar/std"]

On Unix:

Enabling foo-std turns on foo's std feature. It doesn't turn on
main's foo feature, because foo is only optional on Windows.

Enabling bar-std turns on bar's std feature. It doesn't turn on
main's bar feature, because bar is never optional.

Previously, guppy also turned on:

main's foo feature on Unix.

main's bar feature on all platforms.

guppy now matches Cargo:

foo/std only turns on main's foo feature if an optional declaration
of foo applies to the platform. Here, that is true only on Windows.

bar has no optional declarations, so bar/std never turns on main's
bar feature.

As part of this change, ConditionalLink::declarations returns Optional,
not Unsplit, for the links from foo-std to dep:foo and to foo.

From the same repository

guppy-rs/guppy

One column per quarter.

0.18.025 Aug 2026Breaking2 sources agree

With the summaries feature, toml is updated to 1.1.4 ( #600 ). Error::TomlSerializeError now wraps toml 1.x's ser::Error , a breaking change for code…

Added

PlatformSpec::Platforms, a new variant holding a list of platforms
(#438, #630), and PlatformSpec::platforms, a constructor that accepts
any iterator of Platform or Arc<Platform>. A query against Platforms is
enabled if it is enabled on at least one of the platforms. Platforms([]) is
the union of no platforms: nothing is enabled on it, not even unconditional
dependencies.

Per-platform results are combined with the same Kleene K3
OR
that guppy already uses to combine a dependency's target specs for a single
platform: Enabled wins, then Unknown, then Disabled.

Changed

Queries and link visitors:
- PackageQuery and FeatureQuery are now represented as a set of initial
  nodes plus a direction, sharing their internal bitset representation with
  PackageSet and FeatureSet (#609, #610).
  - PackageQuery::initials now returns a &PackageSet, and
    FeatureQuery::initials a &FeatureSet, rather than iterators over
    metadatas. To obtain the old iterators, use
    initials().packages(direction) and initials().features(direction).
  - PackageQuery::starts_from and FeatureQuery::starts_from are removed.
    Use initials().contains(id) instead, which returns the same
    Result<bool, Error>.
  - The Debug output of both query types now goes through the set types'
    Debug impls. PackageQuery's Debug no longer dumps the entire
    package graph, and FeatureQuery's now prints its initial packages with
    their features.
- The package and feature "resolver" traits are renamed and now receive an
  opaque context (#497, #601, #602, #604):
  - PackageResolver is now PackageLinkVisitor, and FeatureResolver is
    now FeatureLinkVisitor. The "resolver" name was easily confused with
    the Cargo feature resolver, and the trait visits links rather than
    packages or features.
  - accept is now visit_link on both traits.
  - visit_link (and the closures passed to PackageQuery::resolve_with_fn
    and FeatureQuery::resolve_with_fn) takes a &PackageLinkContext or
    &FeatureLinkContext instead of a &PackageQuery or &FeatureQuery.
    The query is available via query(); the context also provides
    direction() and starts_from_initial(&link).
  - CargoSet::with_package_resolver is now
    CargoSet::with_cargo_link_visitor and takes a new CargoLinkVisitor
    trait (in guppy::graph::cargo). Its CargoLinkContext exposes which
    pass the link is being evaluated for (build_platform()), the platform
    specs in effect (platform_spec() and build_dep_platform_spec()), and
    whether dev and build dependencies are under consideration for the link
    (considers_dev_deps and considers_build_deps respectively).
  - With the proptest1 feature, Prop010Resolver is now
    Prop010LinkVisitor and PackageGraph::proptest1_resolver_strategy is
    now proptest1_link_visitor_strategy.
Cargo sets and their inputs:
- CargoOptions::new now defaults to version 3 of the Cargo feature
  resolver
  rather than version 1 (#624). To restore the old behavior, call
  set_resolver(CargoResolverVersion::V1).
- A new CargoSetInputs struct in guppy::graph::cargo combines
  CargoOptions and the features-only set, and CargoSet now keeps a copy
  of the inputs it was built with, available via CargoSet::inputs
  (#627). CargoSet::features_only is removed; use
  inputs().features_only instead.
- With the summaries feature, CargoOptionsSummary is renamed to
  CargoSetInputsSummary, and CargoSet::to_summary uses the inputs the
  set was built with (#625). Each features-only entry now records
  whether the package's base feature is enabled, writing base = false when
  it isn't (#626). The field defaults to true, so existing summaries
  continue to work.
Platform specs:
- PlatformSpec::Platform is removed in favor of PlatformSpec::Platforms
  (see above). With the summaries feature, PlatformSpecSummary::Platform
  is likewise replaced by
  PlatformSpecSummary::Platforms(Vec<PlatformSummary>) (#630).
- A single platform is still serialized as-is, so existing serialized data
  continues to work. Zero or several platforms are serialized as an array
  (target-platform = [] or [[target-platform]]), which older versions of
  guppy cannot read.
- With the summaries feature, PlatformSpecSummary::to_platform_spec now
  returns PlatformSpecSummaryError, which names the platform that could not
  be converted, instead of a bare TargetSpecError (#628). The error also
  records the position of the failing platform within a list, available via
  its index and count methods. Both its Display output and
  Error::InvalidPlatformSpecSummary's name the triple and, for a list, the
  position.
- Malformed platform specs now produce errors that name the offending
  element or key, rather than serde's "data did not match any variant"
  message (#629). The following are rejected: "always" and "any" inside
  a list; spec alongside any platform key such as triple or
  target-features; unknown keys in a platform table; empty triples; and
  spec values other than "always" or "any". (Previously,
  spec = "<triple>" was silently treated as that platform.)
PackageMetadata::minimum_rust_version is renamed to
PackageMetadata::rust_version, replacing the deprecated method of that
name (#616). As a result, rust_version now returns Option<&Version>
rather than Option<&VersionReq>.
- Code that calls .matches(version) on the old return value will fail to
  compile; use version >= *rust_version instead.
- For code that displays or serializes these versions, the output will
  change from a requirement such as >=1.65.0 to a plain version such as
  1.65.0.
With the summaries feature, toml is updated to 1.1.4 (#600).
Error::TomlSerializeError now wraps toml 1.x's ser::Error, a breaking
change for code that names that type. Summaries are parsed strictly
according to the TOML 1.1 specification; documents that the lenient toml
0.5 parser accepted but that are not valid TOML are now rejected.
MSRV updated to Rust 1.91, as required by dependencies.

Removed

The following deprecated APIs are removed (#616):

PackageMetadata::rust_version's old form, deprecated since 0.17.1, which
returned an Option<&VersionReq> with a single >=X.Y.Z comparator
synthesized from the rust-version field. See the rename above for the
replacement.
BuildTarget::doc_tests, deprecated since 0.17.16. Use
BuildTarget::doctest_by_default instead.
PlatformSpec::current, deprecated since 0.17.13. Use
PlatformSpec::build_target instead.
The hidden re-export of the debug_ignore crate at the root of guppy.
Depend on debug-ignore directly if
you need it.

Fixed

FeatureSet::union, intersection, difference and symmetric_difference
now panic, as documented, if the two sets were built from different package
graphs (#608). Previously the check compared self's graph against itself
and could never fire, so mismatched sets silently produced an invalid result.
(The corresponding PackageSet operations already checked this correctly.)
With the summaries feature, rebuilding Cargo set inputs from a summary no
longer silently drops the features-only set (#625).

Open source →

Additional notes

Added

Hakari::structural_excludes and Hakari::is_structural_excluded report
the structural excludes: the packages that are never added to the
workspace-hack, described under Fixed below.

Changed

Hakari::toml_name_map now returns an iddqd::IdOrdMap of TomlNameEntry
values, keyed and ordered by the name each dependency is written out under.
Updated toml to 1.1.4 and toml_edit to 0.25.13.
- HakariConfig::from_str, HakariBuilderSummary::to_string and
  HakariBuilderSummary::write_to_string now return error types from toml
  1.x, and TomlOutError::Toml wraps toml 1.x's ser::Error, a breaking
  change for code that names those types.
- Configuration files are parsed strictly according to the TOML 1.1
  specification; documents that the lenient toml 0.5 parser accepted but
  that are not valid TOML are now rejected.
Updated the re-exported diffy to 0.5.2. hakari does not enable any of
diffy's optional features. To use PatchFormatter::with_color, add a
direct dependency on diffy 0.5 with the color feature enabled.
MSRV updated to Rust 1.91, as required by dependencies.

Fixed

Hakari no longer adds third-party packages that depend on the workspace-hack
package, or on a workspace member that hakari manages, directly or
transitively through normal or build dependencies. (Dev-only dependencies are
ignored, since Cargo permits cycles through them.) This typically happens when a
workspace member is also published and a [patch] section redirects the
published version's workspace-hack dependency back into the workspace. In
that case hakari would end up introducing a cycle (#499).
The fixpoint step of the computation no longer adds workspace packages to
Hakari::computed_map or Hakari::output_map. Previously, a third-party
package that depended on a workspace member could cause that member to be
added to the workspace-hack, which would form a cycle.
Generated names for path and workspace dependencies no longer depend on
camino's Hash implementation, which changed in camino 1.2.3. The
output now matches hakari built against camino 1.2.2 and earlier. Builds
of hakari 0.17.9 against camino 1.2.3 or later produced different names;
those revert to the original names with this release.
Updated guppy to 0.19.0, which fixes a number of bugs around Cargo simulation.
In our testing across several real-world workspaces, we did not find any
where the workspace-hack contents changed. If they changed for you, please
update your workspace-hack Cargo.toml.

0.17.2621 May 20262 sources agree

A node with a self-loop edge -- typically a package with a path dev-dependency on its own crate, or a feature node like base/[base] arising from one -

Fixed

A node with a self-loop edge -- typically a package with a path
dev-dependency on its own crate, or a feature node like base/[base]
arising from one -- was treated inconsistently by several APIs. The root
cause was that self-edges were counted as incoming edges in the SCC and
topological-sort machinery, which transitively confused everything built
on top:

Sccs::externals / forward roots. Previously, a package whose only
incoming edge was its own self-loop was excluded from the set of forward
roots, so callers iterating over
query_workspace().resolve().root_ids(_) did not see it, and forward
link enumeration on it was broken. Now, self-loop edges no longer
disqualify a node from being a forward root: a single-node SCC is
external iff it has no incoming edges from outside its own SCC.
(#586)
Topological sort. Previously, TopoWithCycles::new filtered
self-looping nodes out of its root set for the same reason, dropping
them from the DFS and then placing them and their descendants at the
end of the topological order via a best-effort fallback. Now, the
root-set predicate accepts a node whose only incoming edge is its own
self-loop, so such nodes are visited in DFS order alongside other
roots. (#589)
Cycles::is_cyclic and feature::Cycles::is_cyclic. Previously,
these were reflexively true for every package or feature, regardless
of actual cycle membership. Now, they return true only when the
argument lies on a directed cycle: either in a multi-node SCC, or in a
single-node SCC with a self-loop edge. This is a behavior change, but
in the context of the rest of this release is being treated as a
bugfix. (#590)
Cycles::all_cycles and feature::Cycles::all_cycles. Previously,
these reported only SCCs of two or more elements. Now, they also yield
single-node SCCs whose node has a self-loop edge, in topological order
alongside multi-node SCCs. This makes all_cycles() and
is_cyclic(x, x) agree on what counts as a cycle. (#590)
FeatureGraphWarning::SelfLoop. Previously, this warning was
emitted for every self-loop edge in the feature graph, including
legitimate ones such as a path dev-dependency on the package's own
crate. Now, it is restricted to named-feature self-loops like
[features] a = ["a"], which really are user errors. (#592)

Documentation

PackageGraph::directly_depends_on and
FeatureGraph::directly_depends_on. Previously, both documented
themselves as returning false when the two IDs were equal. The
implementation has always called dep_graph.contains_edge(a, b),
which correctly returns true for self-loop edges, so the
documentation contradicted the behavior. The documentation has now
been corrected to match.
FeatureGraph::directly_depends_on. Previously, the docstring
read "returns true if feature_a is a direct dependency of
feature_b," with the operands inverted relative to the actual
implementation. Now the docstring reflects the implementation:
returns true if feature_b is a direct dependency of feature_a.
(#591)
[Cycles] type-level documentation. Previously, the long-form
documentation talked exclusively about multi-node cycles (like
serde and serde_derive). It now also acknowledges single-node
self-loop cycles as a case.

Open source →

0.17.2531 Jan 20262 sources agree

Cargo metadata generated on Windows is now parseable on Unix. Windows paths are always normalized to forward slashes on Unix, which allows operations

Added

Cargo metadata generated on Windows is now parseable on Unix. Windows paths are always normalized to forward slashes on Unix, which allows operations like .parent() to work. (Cross-platform parsing is not fully tested yet so you might run into issues. Please file a bug if you do.)

Open source →

0.17.2427 Dec 2025

Workspace::build_directory() returns the build directory for intermediate build artifacts (requires Cargo 1.91+).

Added

Workspace::build_directory() returns the build directory for intermediate build artifacts (requires Cargo 1.91+).
Workspace::default_members() and Workspace::default_member_ids() iterate over workspace default members (requires Cargo 1.71+; returns empty iterator for older Cargo versions).
PackageLink::registry() returns the registry URL for a dependency, if it uses a non-default registry.
PackageLink::path() returns the file system path for path dependencies.

Open source →

0.17.2312 Oct 2025

Internal dependency update: cargo_metadata updated to 0.23.0.

Changed

Internal dependency update: cargo_metadata updated to 0.23.0.

Open source →

0.17.2229 Sept 2025

Replaced obsolete doc_auto_cfg with doc_cfg, to fix Rust nightly builds with the doc_cfg flag enabled.

Fixed

Replaced obsolete doc_auto_cfg with doc_cfg, to fix Rust nightly builds with the doc_cfg flag enabled.

Open source →

0.17.2115 Sept 2025

Internal dependency update: cargo_metadata updated to 0.22.0.

Changed

Internal dependency update: cargo_metadata updated to 0.22.0.

Open source →

0.17.2011 Jul 2025

Internal dependency update: cargo_metadata updated to 0.21.0.

Changed

Internal dependency update: cargo_metadata updated to 0.21.0.
- As part of this update, restored compatibility with the unstable bindeps feature -- see this commit.
MSRV updated to Rust 1.86, as required by dependencies.

Open source →

0.17.1930 May 2025

Internal dependency update: cargo_metadata updated to 0.20.0.

Changed

Internal dependency update: cargo_metadata updated to 0.20.0.
Some older versions of Cargo, when the unstable bindeps feature is enabled, generate JSON output that is no longer supported by cargo_metadata. If you run into an error, please update your nightly toolchain. Nightly versions from at least 2024-07 do not appear to produce invalid metadata.
MSRV updated to Rust 1.82.

Open source →

0.17.1829 Apr 2025

CargoSet::with_package_resolver supports passing in a PackageResolver for additional dynamic filtering of dependency edges.

Added

CargoSet::with_package_resolver supports passing in a PackageResolver for additional dynamic filtering of dependency edges.
CargoSet::target_links and host_links return the set of PackageLink instances followed on the target and host platforms, respectively.

Thanks to anforowicz for these contributions!

Open source →

0.17.1722 Feb 2025

Add PlatformEval::target_specs to obtain the list of TargetSpec instances backing a platform evaluator. Thanks to anforowicz for the contribution!

Added

Add PlatformEval::target_specs to obtain the list of TargetSpec instances backing a platform evaluator. Thanks to anforowicz for the contribution!

Open source →

0.17.1615 Feb 2025Deprecated

BuildTarget::doc_tests is now BuildTarget::doctest_by_default. The old name has been deprecated, but is kept around for compatibility.

Added

BuildTarget::test_by_default returns true if tests are run for a build target by default.
BuildTarget::doc_by_default returns true if documentation is enabled for a build target, respectively.

Changed

BuildTarget::doc_tests is now BuildTarget::doctest_by_default. The old name has been deprecated, but is kept around for compatibility.

Open source →

0.17.1515 Feb 2025withdrawn

(This version was yanked due to incorrect documentation.)

Open source →

0.17.1411 Feb 2025

MetadataCommand::env adds environment variables to the cargo metadata command.

Added

MetadataCommand::env adds environment variables to the cargo metadata command.

Thanks to anforowicz for your first contribution!

Open source →

0.17.139 Feb 2025Deprecated

The old method is still available but has been marked deprecated.

Changed

Renamed PlatformSpec::current to PlatformSpec::build_target to indicate that it is determined at build time, not at runtime. The old method is still available but has been marked deprecated.

Open source →

0.17.125 Jan 2025

Added support for custom sparse registries (sparse+https://...). Thanks to jonhoo for your first contribution!

Added

Added support for custom sparse registries (sparse+https://...). Thanks to jonhoo for your first contribution!

Open source →

0.17.1123 Dec 2024

Added support for the upcoming Cargo resolver version 3: within guppy, CargoResolverVersion::V3. Resolver version 3 enables MSRV-aware version resolut

Added

Added support for the upcoming Cargo resolver version 3: within guppy, CargoResolverVersion::V3. Resolver version 3 enables MSRV-aware version resolution in Cargo.

The portion of dependency resolution that guppy works with (package and feature resolution) happens after dependency versions have been resolved and Cargo.lock is refreshed. This means that from guppy's perspective, resolver version 3 is the same as version 2, and CargoResolverVersion::V3 acts as an alias for CargoResolverVersion::V2.

Open source →

0.17.103 Dec 2024

Internal dependency update: cargo_metadata updated to 0.19.1.

Changed

Internal dependency update: cargo_metadata updated to 0.19.1.
MSRV updated to Rust 1.82.

Open source →

0.17.93 Dec 2024

Graphs can now be generated even if the workspace Cargo.toml is within a subdirectory of one of its members. (This is an uncommon situation, but one t

Fixed

Graphs can now be generated even if the workspace Cargo.toml is within a subdirectory of one of its members. (This is an uncommon situation, but one that is supported by Cargo.)

Changed

Internal dependency update: cargo_metadata updated to 0.19.0.

Open source →

0.17.82 Oct 2024

Fixed a case of dependency matching with renamed packages ([#317]).

Fixed

Fixed a case of dependency matching with renamed packages (#317).

Changed

Update target-spec to 3.2.2.

Open source →

0.17.71 Aug 2024

### Changed - Update target-spec to 3.2.1.

Changed

Update target-spec to 3.2.1.

Open source →

0.17.629 Jul 2024

Fixed feature graph construction accidentally inserting self-loops in some cases ([#292]). This was causing cargo-hakari to crash in some workspaces.

Changed

MSRV updated to Rust 1.75.

Fixed

Fixed feature graph construction accidentally inserting self-loops in some cases (#292). This was causing cargo-hakari to crash in some workspaces.
Fixed a small bug in Cargo resolution where packages were incorrectly being marked as activated on the host platform (8666ebc).

Open source →

0.17.54 Feb 2024

The Debug impl for FeatureSet is now more useful. (PRs welcome to make the Debug impls for types like PackageSet more useful as well.)

Changed

The Debug impl for FeatureSet is now more useful. (PRs welcome to make the Debug impls for types like PackageSet more useful as well.)
MSRV updated to Rust 1.73.

Fixed

Cargo build simulations now consider dev-dependencies of proc-macro crates. Previously, we weren't doing so.

Open source →

0.17.429 Nov 2023

Attempted to address PackageGraph creation with artifact dependencies as supported by nightly Rust ([#174]). Note that this is not a complete fix, as

Fixed

Attempted to address PackageGraph creation with artifact dependencies as supported by nightly Rust (#174). Note that this is not a complete fix, as documented at #174.

Open source →

0.17.317 Nov 2023

Fixed a PackageGraph creation edge case ([#158]).

Fixed

Fixed a PackageGraph creation edge case (#158).

Open source →

0.17.214 Nov 2023

Improve PackageGraph creation algorithm to address issues like nextest-rs/nextest#1090.

Fixed

Improve PackageGraph creation algorithm to address issues like nextest-rs/nextest#1090.

Changed

MSRV updated to Rust 1.70.

Open source →

0.17.129 Jul 2023Deprecated

PackageMetadata::rust_version has been deprecated because it returns a VersionReq even though it actually should be a Version. In the next major relea…

Added

PackageMetadata::minimum_rust_version provides the rust-version field of a package as a Version.
PackageMetadata::rust_version has been deprecated because it returns a VersionReq even though it actually should be a Version. In the next major release of guppy, the current definition of rust_version will go away and be replaced with minimum_rust_version.

Open source →

0.17.026 Jun 2023

target-spec updated to version 3.

Changed

target-spec updated to version 3.

Fixed

Proptest strategy creator names updated from prop010_ to proptest1_.

Open source →

0.16.019 Jun 2023

target-spec updated to version 2.

Changed

target-spec updated to version 2.
MSRV updated to Rust 1.66.

Open source →

0.15.28 Jan 2023

PackageMetadata::to_feature_set converts a single package to a FeatureSet.

Added

PackageMetadata::to_feature_set converts a single package to a FeatureSet.

Changed

MSRV updated to Rust 1.62.

Open source →

0.15.15 Dec 2022

Detailed documentation about dependency cycles in Cargo, as part of the `Cycles` struct. Thanks Aria for writing it!

Added

Detailed documentation about dependency cycles in Cargo, as part of the Cycles struct. Thanks Aria for writing it!

Open source →

0.15.07 Nov 2022

guppy::Error::UnknownRegistryName now boxes the internal summary and is smaller as a result.

Changed

guppy::Error::UnknownRegistryName now boxes the internal summary and is smaller as a result.

Open source →

0.14.425 Oct 2022

Internal dependency update: cargo_metadata updated to 0.15.1.

Changed

Internal dependency update: cargo_metadata updated to 0.15.1.

Open source →

0.14.330 Sept 2022

Thanks to Carol Nichols for her contributions to this release!

Changed

Repository location update.
MSRV updated to Rust 1.58.

Thanks to Carol Nichols for her contributions to this release!

Open source →

0.14.229 May 2022

On Windows, guppy now behaves correctly when a path dependency is on a different drive from the workspace ([#642]).

Fixed

On Windows, guppy now behaves correctly when a path dependency is on a different drive from the workspace (#642).

Changed

Internal dependency updates.

Open source →

0.14.118 Mar 2022

Workspace::target_directory returns the target directory provided in the Cargo metadata.

Added

Workspace::target_directory returns the target directory provided in the Cargo metadata.
Workspace::metadata_table returns the freeform workspace.metadata table.

Open source →

0.14.015 Mar 2022

Support for [weak dependencies and namespaced features]:

Added

Support for weak dependencies and namespaced features:

Cargo build simulations now take into account weak dependencies and namespaced features.
Optional dependencies ("dep:foo") and namespaced features ("foo") are now represented as separate nodes in a FeatureGraph, even with Rust versions prior to 1.60.
Feature names are now represented as a new FeatureLabel enum.

Changed

MSRV updated to Rust 1.56.

Open source →

0.13.013 Feb 2022

doc_cfg-based feature labels to rustdoc.

Added

doc_cfg-based feature labels to rustdoc.
MetadataCommand::cargo_command returns the underlying std::process::Command instance.

Changed

guppy::graph::feature::CrossLink renamed to ConditionalLink, and now covers some same-package features. For more, see the documentation for ConditionalLink.
Public dependency bump: target-spec updated to version 1.

Fixed

A small fix to Cargo build simulations (#596).

Open source →

0.12.620 Dec 2021

PackageMetadata::homepage, documentation and default_run, exposed by newer versions of Cargo.

Added

PackageMetadata::homepage, documentation and default_run, exposed by newer versions of Cargo.

Open source →

0.12.517 Dec 2021

guppy now supports a "light" mode if --no-deps is passed in. This mode doesn't provide any information about third-party packages or dependency edges,

Added

guppy now supports a "light" mode if --no-deps is passed in. This mode doesn't provide any information about third-party packages or dependency edges, but is much faster if the only information needed is workspace lookups.

Open source →

0.12.48 Dec 2021

Reverted change in 0.12.3 because of #524.

Reverted change in 0.12.3 because of #524.

Open source →

0.12.329 Nov 2021

Internal dependency guppy-workspace-hack updated to `workspace-hack`.

Internal dependency guppy-workspace-hack updated to workspace-hack.

Open source →

0.12.226 Nov 2021

PackageMetadata::link_between, link_from and link_to look up a direct link from one package to another.

Added

PackageMetadata::link_between, link_from and link_to look up a direct link from one package to another.

Open source →

0.12.124 Nov 2021

The toml crate is now built with the preserve_order feature.

Changed

The toml crate is now built with the preserve_order feature.
- This feature ensures that the key ordering in metadata is preserved.

Open source →

0.12.023 Nov 2021Breaking

This is a minor breaking change that should not affect most consumers.

Fixed

Summaries generated by old versions of guppy can now be parsed by this version, even if the metadata is in a different format.

Changed

Relative paths are now stored and presented with forward slashes on all platforms, including Windows.
guppy-summaries updated to 0.6.0.

Open source →

0.11.320 Nov 2021

PackageMetadata::rust_version returns the package.rust-version field, if specified. Thanks @foresterre!

Added

PackageMetadata::rust_version returns the package.rust-version field, if specified. Thanks @foresterre!

Open source →

0.11.27 Oct 2021

Rudimentary support for alternate registries. This is a temporary workaround until Cargo issue #9052 is resolved.

Added

Rudimentary support for alternate registries. This is a temporary workaround until Cargo issue #9052 is resolved.
- This is currently only hooked up to hakari.

Open source →

0.11.11 Oct 2021

A new abstraction PlatformSpec can represent the union of all platforms, the intersection of all platforms, or a single platform.

Added

A new abstraction PlatformSpec can represent the union of all platforms, the intersection of all platforms, or a single platform.
- Methods like EnabledStatus::required_on and EnabledStatus::enabled_on have been switched to accepting a &PlatformSpec rather than a &Platform.
- CargoOptions::set_platform and related methods now accept either a Platform or a PlatformSpec.
- EnabledStatus::enabled_on_any is now EnabledStatus::enabled_on(&PlatformSpec::Any).
Omitted packages are now easier to describe while deserializing: they now take a workspace-members list of names, and a third-party list of specifiers such as { name = "serde", version = "1" }.
- The resolver will now also fail if any specifiers are unmatched.

Changed

Platform-related types have been moved into the new platform module at the top level.
In Cargo options summaries, version = "v1" and version = "v2" have been renamed to resolver = "1" and resolver = "2" respectively, to align with Cargo.
- The old specifiers will continue to work.
Because of the changes to how omitted packages are represented, old-style CargoOptionsSummary instances may no longer parse correctly.
MSRV updated to Rust 1.53.

Open source →

0.11.01 Oct 2021withdrawn

(This release was incorrectly made and was yanked.)

Open source →

0.10.114 Sept 2021

Public dependency version bumps:

Changed

Public dependency version bumps:
- target-spec updated to 0.8.0.
  - As a result, Platform no longer has a lifetime parameter.
- guppy-summaries updated to 0.5.0.
- semver updated to 1.0.
MSRV updated to Rust 1.51.

Open source →

0.10.014 Sept 2021withdrawn

(This release was yanked because guppy-summaries needed to be upgraded as well.)

(This release was yanked because guppy-summaries needed to be upgraded as well.)

Open source →

0.9.011 Mar 2021

DependencyKind::VALUES lists out all the values of DependencyKind.

Added

DependencyKind::VALUES lists out all the values of DependencyKind.
DependencyReq::no_default_features() returns the enabled status for a dependency when default-features = false.

Changed

PackageMetadata::publish now returns a new, more descriptive PackagePublish enum (#320).
PackageMetadata::readme now returns &Utf8Path rather than &Path.
BuildTarget::path now returns &Utf8Path rather than &Path.

Open source →

0.8.024 Feb 2021Breaking

…ordering of nested metadata tables. This is a breaking change for code that names the following types:

Changed

Updated toml to 1.1.4. The on-disk format written by
Summary::write_to_string is unchanged: summaries are now written by the new
toml_compat module, which reproduces the output of toml 0.5's pretty
serializer, including its ordering of nested metadata tables. This is a
breaking change for code that names the following types:
- Summary::metadata is now toml 1.x's Table.
- Summary::parse, Summary::with_metadata, Summary::to_string and
  Summary::write_to_string return toml 1.x's error types.
- Summary::with_metadata no longer rejects metadata whose fields are
  declared out of TOML emission order; the fields are reordered when the
  summary is constructed instead.
- SummaryDiff is still serialized with toml's own serializer, whose
  blank-line placement differs slightly from 0.5.
Summaries are parsed strictly according to the TOML 1.1 specification;
documents that the lenient toml 0.5 parser accepted but that are not valid
TOML are now rejected.
MSRV updated to Rust 1.91, as required by dependencies.

Open source →

Additional notes

Changed

guppy now uses camino Utf8Path and Utf8PathBuf wrappers. These wrappers provide type-level assertions that returned paths are valid UTF-8.
Public dependency version bumps:
- proptest updated to version 1 and the corresponding feature renamed to proptest1.

Open source →

0.7.217 Feb 2021

Restored compatibility with Rust 1.48. (1.48 is the MSRV, and is now tested in CI.)

Fixed

Restored compatibility with Rust 1.48. (1.48 is the MSRV, and is now tested in CI.)

Open source →

0.7.114 Feb 2021Breaking

…then Foo is returned before Bar. (This is not a breaking change because it is an additional constraint on guppy itself, not on its consumers.)

Changed

Packages within a cycle are now returned in non-dev order. When the direction is forward, if package Foo has a dependency on Bar, and Bar has a cyclic dev-dependency on Foo, then Foo is returned before Bar. (This is not a breaking change because it is an additional constraint on guppy itself, not on its consumers.)

Open source →

0.7.04 Feb 2021

PackageSource now has support for parsing external sources through a new parse_external method.

Added

PackageSource now has support for parsing external sources through a new parse_external method.
Cargo simulations have some new features:
- New CargoOptions::set_initials_platform method can be used to simulate builds on exclusively the host platform.
- CargoSet::new accepts an additional argument, features_only, which represents additional inputs that are only used for feature unification. This may be used to simulate, e.g. cargo build --package foo --package bar, when you only care about the results of foo but specifying bar influences the build.
- New enum graph::cargo::BuildPlatform represents either the target platform or the host. New methods CargoSet::platform_features and CargoSet::platform_direct_deps accept the BuildPlatform enum.
FeatureSet::contains_package returns true if a feature set has at least one feature in the given package.
semver::VersionReq is now exposed in guppy.
FeatureGraph::resolve_ids resolves feature IDs into a FeatureSet.

Changed

Feature filters all_filter, default_filter and none_filter have been combined into a single enum StandardFeatures.
Cargo builds are now done through FeatureSet instances, not FeatureQuery. This is because Cargo builds always happen in the forward direction.
- FeatureQuery::resolve_cargo has been renamed to FeatureSet::into_cargo_set.
CargoOptions::with_ methods have been renamed to begin with either set_ or add_.
Obs is now a type rather than a trait.
CargoOptions::set_proc_macros_on_target was replaced with InitialsPlatform::ProcMacrosOnTarget.
Public dependency version bumps:
- semver updated to 0.11.
- target-spec updated to 0.6.

Open source →

0.6.311 Jan 2021

Fix an unintentional use of serde's private exports.

Fixed

Fix an unintentional use of serde's private exports.

Open source →

0.6.210 Dec 2020

FeatureGraph::is_default_feature no longer follows cross-package links.

Fixed

FeatureGraph::is_default_feature no longer follows cross-package links.

Cyclic dev-dependencies can enable non-default features (such as testing-only features), and previously is_default_feature would have returned true for such features. With this change, is_default_feature returns false for such features.

The default_filter feature filter, which uses is_default_feature, has been fixed as well.

Open source →

Your coding agent can read these notes before it upgrades. Set up the MCP server →