chore(deps): bump gix-packetline from 0.21.3 to 0.22.2 in /fuzz in the cargo group across 1 directory

[dependabot]

Bumps the cargo group with 1 update in the /fuzz directory: gix-packetline.

Updates gix-packetline from 0.21.3 to 0.22.2

Release notes

Sourced from gix-packetline's releases.

gix-packetline v0.22.2

Commit Statistics

• 1 commit contributed to the release over the course of 1 calendar day.
• 1 day passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Merge pull request #2932 from GitoxideLabs/fundamental-types-comp (6704303)

gix-packetline v0.22.1

Commit Statistics

• 2 commits contributed to the release over the course of 30 calendar days.
• 31 days passed between releases.
• 0 commits were understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details

• Uncategorized
  • Use fundamental-type comparisons throughout tests (47536a5)
  • Merge pull request #2812 from GitoxideLabs/report-july (ae8845a)

Changelog

Sourced from gix-packetline's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

New Features

• add configurable terminal screen modes.

• hide revision ancestry in tix

• add tix to the gix CLI

• add explicit gix config show subcommand.

• add gix config list for showing the git-configuration files.

• add the gix config fmt subcommand Expose the gix-config whitespace formatter as gix config fmt [--in-place] [in-file] [out-file]: with no in-file it formats the repository-local configuration, and with no out-file it writes to stdout. The repository is only opened when the repository-local configuration is needed, so formatting an explicit file works outside a repository too.

• add gix status --untracked flag This allows to control how untracked files are folded, but also can completely turn dirwalking off.

• add gix free remote refs to list and write remote refs. Add gix free remote refs to perform an upload-pack handshake, discover the remote reference advertisement, and print the refs without negotiating or receiving a pack.

  The command can also write the advertised refs into a standalone ref store:

  gix free remote refs --refs-directory out-refs <url>

Bug Fixes

• preserve multiple remote URLs Configured remotes can have multiple remote..url or remote..pushUrl values, but gix::Remote kept only one value because lookup used the singular config accessor. That meant the most recent config value won, while Git exposes every effective URL and uses the first one for the singular get-url form.

  Add ordered URL storage to gix::Remote and expose Remote::urls(Direction) for all effective URLs. Keep Remote::url(Direction) as the singular compatibility API, now returning the first effective URL. Fetch URLs used as push fallbacks try pushInsteadOf first and then insteadOf, matching Git behavior.

... (truncated)

Commits

• 3ebca8b Release gix-packetline v0.22.2, gix-worktree-stream v0.36.1, gix-archive v0.3...
• 209fb85 feat(gix-macros): replace the withdrawn bisync dependency (#2939)
• 2825d97 Merge pull request #2937 from SebTardif/fix/conflict-skip-consecutive-path
• 6be36bc review
• 4fa211d Merge pull request #2936 from GitoxideLabs/fixup-pack-creation
• 251e0f5 fix: skip only consecutive same-path conflict stages
• 4009a9a fix(gix-pack): retain additions from all merge parents (#2935)
• 0f837c0 Merge pull request #2931 from cruessler/make-slider-test-more-granular
• 169ae96 review
• 7192d9a add optional detailed report to slider test
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The review indicates that the PR is structurally incomplete despite meeting general quality standards. The primary concern is the omission of changes to the manifest file. Since the update involves a minor version increment for a zero-point crate, the build system's semantic versioning logic requires an explicit manifest update to resolve the new version. Without this change, the dependency upgrade will not be effectively applied to the fuzzer targets.

About this PR

• The changes include an update to the lockfile but lack the necessary modifications to the manifest file. For crates using zero-point versioning, a minor version increment is treated as a breaking change, requiring an explicit update in the manifest to allow the resolution of the new version.

Test suggestions

• Verify that fuzzer targets in /fuzz compile successfully with the updated dependency version

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that fuzzer targets in /fuzz compile successfully with the updated dependency version

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud