Update Rust crate guppy to v0.17.26

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
guppy	dependencies	patch	0.17.7 → 0.17.26

---

Release Notes

guppy-rs/guppy (guppy)

v0.17.26: guppy 0.17.26

Compare Source

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.

v0.17.25: guppy 0.17.25

Compare Source

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

v0.17.24: guppy 0.17.24

Compare Source

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.

v0.17.23: guppy 0.17.23

Compare Source

Changed

• Internal dependency update: cargo_metadata updated to 0.23.0.

v0.17.22: guppy 0.17.22

Compare Source

Fixed

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

v0.17.21: guppy 0.17.21

Compare Source

Changed

• Internal dependency update: cargo_metadata updated to 0.22.0.

v0.17.20: guppy 0.17.20

Compare Source

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.

v0.17.19: guppy 0.17.19

Compare Source

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.

v0.17.18: guppy 0.17.18

Compare Source

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!

v0.17.17: guppy 0.17.17

Compare Source

Added

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

v0.17.16: guppy 0.17.16

Compare Source

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.

v0.17.15: guppy 0.17.15

Compare Source

Added

• BuildTarget::tests_enabled and BuildTarget::docs_enabled return true if tests and documentation is enabled for a build target, respectively.

Changed

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

v0.17.14: guppy 0.17.14

Compare Source

Added

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

  Thanks to anforowicz for your first contribution!

v0.17.13: guppy 0.17.13

Compare Source

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.

v0.17.12: guppy 0.17.12

Compare Source

Added

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

v0.17.11: guppy 0.17.11

Compare Source

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.

v0.17.10: guppy 0.17.10

Compare Source

Changed

• Internal dependency update: cargo_metadata updated to 0.19.1.
• MSRV updated to Rust 1.78.

v0.17.9: guppy 0.17.9

Compare Source

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.

v0.17.8: guppy 0.17.8

Compare Source

Fixed

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

Changed

• Update target-spec to 3.2.2.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.