chore(deps): update dependency sphinx-autodoc-typehints to v3.13.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sphinx-autodoc-typehints (changelog)	==3.13.5 → ==3.13.6

---

Release Notes

tox-dev/sphinx-autodoc-typehints (sphinx-autodoc-typehints)

v3.13.6

Compare Source

What's Changed

• 🐛 fix(annotations): defer alias expansion by @​flying-sheep in #​766

Full Changelog: tox-dev/sphinx-autodoc-typehints@3.13.5...3.13.6

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

LGTM, straightforward dependency version bump.

What was reviewed: the single-line diff in requirements-dev.txt bumping sphinx-autodoc-typehints (a dev-only doc-building dependency) from 3.13.5 to 3.13.6 — confirmed no other lines changed and no source/test files are touched.

Extended reasoning...

Overview

The change is a one-line patch-version bump of sphinx-autodoc-typehints (3.13.5 → 3.13.6) in requirements-dev.txt, a dev-only dependency used solely for building Sphinx documentation. No application source, tests, or runtime dependencies are affected.

Security risks

None identified. The package is a documentation build-time tool, not part of the runtime dependency graph, so it has no exposure to production code paths, user input, or secrets. The upstream release notes cite a single bug fix (deferred alias expansion), not a security patch, and this is an automated Renovate PR pinning an exact version.

Level of scrutiny

Minimal scrutiny is appropriate: this is a mechanical, single-line, dev-dependency version bump with no ambiguity in intent or effect. No CODEOWNERS file restricts this path, and there is no prior review history or outstanding objections to account for.

Other factors

No tests are relevant to a doc-tooling dependency bump, and the diff is fully self-contained and easily verifiable by inspection, which was done directly against the diff command output.