chore(deps): bump gix from 0.84.0 to 0.85.0

[dependabot]

Bumps gix from 0.84.0 to 0.85.0.

Release notes

Sourced from gix's releases.

gix v0.85.0

Bug Fixes (BREAKING)

• avoid duplicate network connection when adopting a remote-controlled hash kind. Connections can now be created from detached remotes, internally, which makes them independent of the underlying repository.

  This is breaking as it comes with a cleanup of Connection lifetimes, which will break anyone who stores them in a struct. So hopefully nobody is affected.

• bound the clone object-hash adoption retry The clone fetch loop adopts the remote's object format and retries when it differs from the freshly initialized local repository. Adoption makes the next iteration's hashes match, but if the reopened repository somehow still disagrees the loop would re-handshake forever. Track whether we already retried and fail with IncompatibleObjectHash on a second mismatch instead. The error variant is introduced here, as this is its only user.

  Also silence clippy::never_loop on default (sha1) features, where the sha256-gated continue is absent and the loop always returns first pass.

New Features (BREAKING)

• add leaf-only tree-editor removal via Editor::remove_leaf() Motivation comes from gitbutlerapp/gitbutler#14312, where callers had to split tree-entry deletions from additions to avoid accidentally deleting a newly-added subtree after adding A/one and then deleting A.

  Add Editor::remove_leaf() to gix-object and expose it through gix object tree editors and cursors. The new API keeps remove() behavior unchanged, remains tolerant of absent paths, but returns an error when the target entry exists and is a tree.

Bug Fixes

• adopt the remote's object format when cloning A clone into a freshly initialized repository hit an unimplemented! panic when the remote used sha256, since the local repository defaults to sha1.

  Reconfigure the still-empty local repository to the remote's object format and retry the fetch, matching git's behavior of inheriting the remote's hash on clone.

  Without the sha256 feature gix_hash::Kind has a single variant, so the local and remote hashes can never differ; the mismatch check is compiled out entirely in that case.

• write fetched remote symrefs as direct refs Previously gix had made-up behaviour to 'improve' on standard Git,

... (truncated)

Commits

• 6428edc Release gix-date v0.15.5, gix-hashtable v0.15.2, gix-object v0.62.0, gix-attr...
• 1d301e2 report for June 2026
• da6b267 Merge pull request #2642 from 10ne1/dev/aratiu/sha256-transport
• 3927d70 Add journey-tests for SHA-256 clones and ref-lists
• 9929ece fix!: avoid duplicate network connection when adopting a remote-controlled ha...
• ed998d1 review
• f7d6608 Merge pull request #2664 from ameyypawar/docs/2421-index-write-tree-cache
• 325d2a1 map fetch pack/index checksums to their SHA-256 values
• a507ee0 Merge pull request #2661 from GitoxideLabs/negative-refspec-parsing
• 470e689 derive update_refs expected ids from the fixture (hash-aware)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)