fix(deps): update rust crate gix-traverse to 0.61 - autoclosed

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
gix-traverse	dependencies	minor	0.60 → 0.61

---

Release Notes

GitoxideLabs/gitoxide (gix-traverse)

v0.61.0: gix-traverse v0.61.0

Compare Source

Bug Fixes

• ignore duplicate topo traversal tips

  Repeated starting commits were inserted into the topological queue more than
  once, which could duplicate the tip and truncate walks depending on sorting.
  The regression compares one tip with the same tip supplied twice for both
  topological and date ordering, with and without a commit graph.

  Ignore repeated tips at the builder boundary while preserving their
  first-seen order. This matches Git's duplicated-head behavior covered by
  t/t6003-rev-list-topo-order.sh.

New Features (BREAKING)

• add commit::Info::generation
  That way it's evident if a commit-graph was present for this node.
  Breaking, as it adds a new public field to a structure.

Commit Statistics

• 10 commits contributed to the release over the course of 30 calendar days.
• 30 days passed between releases.
• 2 commits were understood as conventional.
• 1 unique issue was worked on: #​2902

Commit Details

view details

• #​2902
  • Ignore duplicate topo traversal tips (75f1a01)
• Uncategorized
  • Update manifests prior to release (ebe9095)
  • Merge pull request #​2905 from GitoxideLabs/various-improvements (f3bbfad)
  • Adapt to changes in gix-testtools (0cbe539)
  • Merge pull request #​2901 from cruessler/switch-to-gix-odb-at-opts (2a4d996)
  • Introduce Store::at() where possible (17fea2a)
  • Merge pull request #​2903 from GitoxideLabs/traverse-dupl-tip (70e98a0)
  • Merge pull request #​2839 from GitoxideLabs/tix-improvements (4b3bf5a)
  • Add commit::Info::generation (e768682)
  • Merge pull request #​2812 from GitoxideLabs/report-july (ae8845a)

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet]

What changed upstream: gix-traverse 0.61 is a minor bump — a topo-walk dedup bugfix, plus a "breaking" addition of a public generation field on commit::Info. Nothing here removes/renames an API this repo uses.

Blocking: this bump breaks the build, and it's not the changelog's fault. gix-traverse is also used directly in src/git/tags.rs:4 (use gix_traverse::commit::simple::CommitTimeOrder;) alongside gix::revision::walk::Sorting (src/git/tags.rs:238, Sorting::ByCommitTime(CommitTimeOrder::NewestFirst)). gix 0.86.0 is untouched by this PR and still depends internally on gix-traverse 0.60 — confirmed in the Cargo.lock diff, which now carries both gix-traverse 0.60.0 (via gix) and gix-traverse 0.61.0 (direct), plus duplicated gix-actor/gix-object/gix-date/gix-error/gix-chunk/gix-commitgraph/gix-revwalk. Cargo treats 0.60 and 0.61 as semver-incompatible, so Sorting::ByCommitTime (expecting gix's 0.60-flavored CommitTimeOrder) no longer accepts the 0.61 CommitTimeOrder this file imports — a type mismatch, not a flake. That's exactly why Test, Coverage, and Build micro bench binary all fail on this head SHA while the non-compiling scans (secrets/CVE/lint) stay green.

Fix isn't a one-line suggestion here: gix-traverse needs to move in lockstep with gix. gix 0.87.0 depends on gix-traverse ^0.61.0, so this PR should also bump gix 0.86 → 0.87 in Cargo.toml to collapse the graph back to one gix-traverse version. Don't just pin gix-traverse back to 0.60 to make CI green — that defeats the update; hold this PR (or widen it to include the gix bump) until the two move together.

[github-actions]

SonarQube — aucune nouvelle issue

_{Comparaison entre le projet bac à sable de cette PR et la branche par défaut : SonarQube Community n'analyse pas les PR, ce delta est calculé côté CI. Détail}