chore(deps): bump vulnerable dev-only tooling

[ehe9991]

Problem

uv.lock pins dev tooling with critical/high advisories: GitPython 3.1.49 (26 advisories, 1 critical; via tach), tornado 6.5.5 (10; via ipykernel), virtualenv 21.3.0 (4; via pre-commit), setuptools 82.0.1 (via pyinstaller) and datamodel-code-generator 0.57.0 (11; dev extra).

pip users never install these, but the release binary does bundle tornado: release.yml builds from an env that includes the dev group. A separate PR keeps dev packages out of the binary.

Solution

• Lock bumps: GitPython 3.2.0, tornado 6.5.10, virtualenv 21.14.5, setuptools 84.0.0, datamodel-code-generator 0.83.0. Transitive: python-discovery 1.6.1, typing-extensions 4.16.0.
  • GitPython 3.2.0, not 3.1.62: the 3.1 line gets no further releases. 3.2.1 is under a day old.
  • tornado 6.5.10, not 6.5.9: 6.5.9's StaticFileHandler symlink change broke Jupyter, and 6.5.10 fixes that.
• datamodel-code-generator 0.61+ blocks private-network schema URLs, so --env dev (localhost) now passes --allow-private-network. Prod and custom URLs keep the default protection.
• Supply chain: all targets were published at least 7 days ago; python-discovery is held at 1.6.1 because 1.6.3 is from today. Publishers are unchanged except one transfer: datamodel-code-generator's repo moved from koxudaxi/ to the datamodel-code-generator org (2026-09-07). koxudaxi is its only public member and still the PyPI owner, so I accepted it. All 22 changed artifact hashes match PyPI.

Testing

• datamodel-code-generator 0.57.0 and 0.83.0 produce byte-identical service_types.py from the current prod spec (timestamp aside).
• --env dev now fails on connection refused (no local server) instead of the private-network block.
• CI green: tests on 3.10–3.14, lint, cli-test. Locally: uv lock --check, 846 pytest passed, ruff, tach (exercises GitPython 3.2.0), ty, and pre-commit run --all-files (builds hook envs with virtualenv 21.14.5).

Supersedes Dependabot #129, #135, #136, #137.

🤖 Generated with Claude Code