build(deps): bump tar from 0.4.44 to 0.4.46 in /tools/argument-comment-lint in the cargo group across 1 directory

[dependabot]

Bumps the cargo group with 1 update in the /tools/argument-comment-lint directory: tar.

Updates tar from 0.4.44 to 0.4.46

Release notes

Sourced from tar's releases.

0.4.46

Security

• archive: Fix another PAX header desync (GHSA-3cv2-h65g-fgmm) by @​cgwalters in composefs/tar-rs#454

See also GHSA-3cv2-h65g-fgmm

Other changes

• ci: Fix and re-enable reverse dependency testing by @​cgwalters in composefs/tar-rs#444
• Update astral-tokio-tar requirement from 0.5 to 0.6 by @​dependabot[bot] in composefs/tar-rs#446
• Update some links by @​atouchet in composefs/tar-rs#445
• Add support of absolute paths by @​zxvfc in composefs/tar-rs#426
• docs: Expand notes on concurrent mutations and following symlinks by @​cgwalters in composefs/tar-rs#453
• Update repo links by @​cgwalters in composefs/tar-rs#451
• ci: Add crates.io trusted publishing workflow by @​cgwalters in composefs/tar-rs#456
• Release 0.4.46 by @​cgwalters in composefs/tar-rs#455

New Contributors

• @​dependabot[bot] made their first contribution in composefs/tar-rs#446
• @​atouchet made their first contribution in composefs/tar-rs#445
• @​zxvfc made their first contribution in composefs/tar-rs#426

Full Changelog: composefs/tar-rs@0.4.45...0.4.46

Commits

• fc459c1 Release 0.4.46
• 43e05a8 ci: Add crates.io trusted publishing workflow
• bba5666 Update repo links
• cd94c46 docs: Document TOCTOU / concurrent-mutation threat model
• 1b4997c builder: Expand docs for follow_symlinks and append_dir_all
• bab14dd archive: Fix another PAX header desync (GHSA-3cv2-h65g-fgmm)
• 2349b49 Add support of absolute paths
• 39d0311 Update some links
• 59d803e Update astral-tokio-tar requirement from 0.5 to 0.6
• 8296b9a ci: Fix and re-enable reverse dependency testing (#444)
• 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.

[nuntius-review]

Vesper

Reviewed commits

Commit	Summary
58846ca	build(deps): bump tar

The changes in Cargo.lock show an upgrade of the tar crate (from 0.4.44 to 0.4.46) and a downgrade of the windows-sys dependency (from 0.61.2 to 0.52.0) for several packages.

Analysis

1. Correctness & Consistency:

   • Cargo.lock is a machine-generated file. Manual edits to this file are highly discouraged as they can easily lead to dependency resolution errors or mismatched checksums.
   • If these changes were generated automatically by running cargo update or modifying Cargo.toml, they are correct and safe to commit.
   • If they were edited manually, you should revert the manual changes and run cargo update -p tar or the appropriate cargo commands to let the package manager resolve the dependencies cleanly.

2. Windows Compatibility:

   • Downgrading windows-sys from 0.61.2 to 0.52.0 is common when targeting older Rust toolchains or maintaining compatibility with crates that haven't updated their APIs to the newer windows-sys versions yet.
   • Ensure that you run cargo check --target x86_64-pc-windows-msvc (or your target Windows triple) to verify that the downgrade does not break any Windows-specific platform code in your workspace.

No direct code changes are recommended for this file, as any adjustments should be performed via the cargo CLI rather than manual edits.