Skip to content

build(deps): refresh uv.lock — resolve all 99 Dependabot alerts - #48

Merged
vemuribv merged 1 commit into
mainfrom
chore/uv-lock-refresh-2026-11
Nov 16, 2026
Merged

vemuribv merged 1 commit into
mainfrom
chore/uv-lock-refresh-2026-11

Conversation

@vemuribv

Copy link
Copy Markdown
Collaborator

Summary

Refreshes uv.lock to resolve all 99 open Dependabot alerts (7 critical, 47 high, 38 moderate, 7 low at the time of the refresh). Every alert was in uv.lock, which pins CI and contributor environments only: pyproject.toml sets minimum versions, so PyPI installs of ddharmon were already resolving patched releases.

Only the 14 flagged packages were upgraded (uv lock --upgrade-package …); everything else keeps its locked version:

Package Before After
pillow 12.2.0 13.0.0
torch 2.10.0 2.15.0
soupsieve 2.8.4 4.1.1
filelock 3.24.3 4.2.10
tornado 6.5.7 6.6.1
setuptools 82.0.0 84.2.1
fsspec 2026.2.0 2026.9.0
anyio 4.12.1 4.16.0
certifi 2026.2.25 2026.10.23
urllib3 2.7.0 2.8.0
black 26.5.1 26.10.1
jupyterlab 4.6.2 4.6.6
notebook 7.6.0 7.6.5
nbconvert 7.17.1 7.17.2

The torch bump is the big one. Every patched torch release (≥ 2.13, including a pinned 2.13.0) defaults to the CUDA 13 wheels on Linux, so the lock swaps the nvidia-*-cu12 stack for CUDA 13 (30 nvidia packages, cuda-bindings / cuda-toolkit, triton 3.9.0). CI runs on CPU and is unaffected, and torch 2.15 is what pip install ddharmon[all] resolves today anyway. The alternative is to hold torch at 2.10 and leave its one low-severity alert open.

The lock also catches up with pyproject.toml: the project's own version (1.1.0 → 1.4.1) and the sources extra (pypdf, python-docx), which the previous lock was missing.

Verification

  • Every open alert checked against the new lock: 99 / 99 resolved (no locked version inside a vulnerable range)
  • uv lock --check passes; uv sync --extra dev --locked (CI's install): ruff clean, black reformats nothing under 26.10.1, pyright 0 errors, pytest 1157 passed, 4 skipped, 6 integration deselected (same as the 1.4.1 release run)
  • uv sync --all-extras --locked installs; scripts/smoke_test.py --expected 1.4.1 --full passes all 7 checks, including the real BioLORD embed → cluster → anchor pipeline on torch 2.15 / pillow 13
  • scripts/leak_scan.py: clean

No release needed: nothing in the published package changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MseUcfWKEBkHCT5f3xQ5vZ

Upgrades only the 14 flagged packages (uv lock --upgrade-package): pillow 13.0.0, anyio 4.16.0, certifi 2026.10.23,
black 26.10.1, filelock 4.2.10, fsspec 2026.9.0, jupyterlab 4.6.6, nbconvert 7.17.2, notebook 7.6.5, setuptools
84.2.1, soupsieve 4.1.1, tornado 6.6.1, urllib3 2.8.0 and torch 2.15.0. Every patched torch release defaults to the
CUDA 13 wheels on Linux, so the torch bump also swaps the nvidia-*-cu12 stack for CUDA 13 and moves triton to 3.9.0.
The lock also catches up with pyproject.toml: the project's own version (1.1.0 -> 1.4.1) and the `sources` extra
(pypdf, python-docx).

The lockfile pins CI and contributor environments only; PyPI installs resolve from pyproject.toml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MseUcfWKEBkHCT5f3xQ5vZ
@vemuribv
vemuribv merged commit 63618d6 into main Nov 16, 2026
3 checks passed
@vemuribv
vemuribv deleted the chore/uv-lock-refresh-2026-11 branch November 16, 2026 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant