Repository navigation
build(deps): refresh uv.lock — resolve all 99 Dependabot alerts - #48
Merged
Merged
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes
uv.lockto resolve all 99 open Dependabot alerts (7 critical, 47 high, 38 moderate, 7 low at the time of the refresh). Every alert was inuv.lock, which pins CI and contributor environments only:pyproject.tomlsets minimum versions, so PyPI installs ofddharmonwere already resolving patched releases.Only the 14 flagged packages were upgraded (
uv lock --upgrade-package …); everything else keeps its locked version: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-*-cu12stack 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 whatpip 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 thesourcesextra (pypdf,python-docx), which the previous lock was missing.Verification
uv lock --checkpasses;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 --lockedinstalls;scripts/smoke_test.py --expected 1.4.1 --fullpasses all 7 checks, including the real BioLORD embed → cluster → anchor pipeline on torch 2.15 / pillow 13scripts/leak_scan.py: cleanNo release needed: nothing in the published package changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MseUcfWKEBkHCT5f3xQ5vZ