🔒️ [+security] Upgraded dependencies based on uv audit

[davidbrownell]

uv audit reported security vulnerabilities in the following packages; uv.lock has been
updated to upgrade them.

Package    From    To      Advisories
---------  ------  ------  ------------------------------------------------------------------
gitpython  3.1.58  3.1.62  PYSEC-2026-3785, PYSEC-2026-3786, PYSEC-2026-3787, PYSEC-2026-3788

Advisories

• PYSEC-2026-3785 (gitpython 3.1.58, fixed in 3.1.59): GitPython before 3.1.59 fails to disable merge_includes when parsing .gitmodules, allowing attackers to disclose local file content by including arbitrary file paths via [include] directives. Attackers can craft a malicious .gitmodules file with include directives pointing to sensitive files; when repo.submodules is accessed, GitConfigParser raises MissingSectionHeaderError embedding the target file's first line verbatim in the exception message. details
• PYSEC-2026-3786 (gitpython 3.1.58, fixed in 3.1.59): GitPython before 3.1.59 fails to safely re-serialize multi-line git-config values during write operations, corrupting dormant quoted values into injected directives like core.hooksPath. Attackers can craft config files with embedded newlines that become live git directives after any unrelated GitPython config write, enabling arbitrary code execution via hook invocation. details
• PYSEC-2026-3787 (gitpython 3.1.58, fixed in 3.1.59): GitPython before 3.1.59 omits --separate-git-dir from unsafe_git_clone_options, allowing attackers to create arbitrary git directories outside the intended clone destination. Attackers can pass a separate_git_dir parameter to Repo.clone_from() or Repo.clone() to redirect repository metadata to an attacker-controlled filesystem path, enabling arbitrary directory creation and potential hook execution. details
• PYSEC-2026-3788 (gitpython 3.1.58, fixed in 3.1.59): GitPython versions before 3.1.59 contain an incomplete denylist in the unsafe_git_revision_options guard that omits --contents and -S options, allowing attackers to read arbitrary files by passing these options to Repo.blame(). Attackers can supply revision values like --contents=/etc/passwd to leak file contents through the blame result returned to the caller. details