Skip to content

chore(deps): upgrade packages flagged by pip-audit - #27

Merged
Trosper3 merged 1 commit into
mainfrom
chore/pip-audit-upgrades
Nov 17, 2026
Merged

Trosper3 merged 1 commit into
mainfrom
chore/pip-audit-upgrades

Conversation

@wrigjl

@wrigjl wrigjl commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

The rbs audit gate is failing on main's lock file (for example on #26). This upgrades every package pip-audit flags. Only uv.lock changes; pyproject.toml pins are untouched.

Package From To Pulled in by
werkzeug 3.1.8 3.1.9 Flask (runtime)
urllib3 2.7.0 2.8.0 requests (runtime)
certifi 2026.6.17 2026.10.23 requests (runtime)
black 26.5.1 26.10.1 dev group
pip 26.1.2 26.3 pip-audit → pip-api (dev)
filelock 3.29.5 4.2.11 pip-audit → cachecontrol (dev), major bump
msgpack 1.2.1 1.2.4 pip-audit → cachecontrol (dev)

Testing

  • pip-audit: no known vulnerabilities.
  • The new black reformats nothing; ruff is clean. pip-audit itself still works with filelock 4.x.
  • Runtime packages were upgraded one at a time, with the unit tests (65) passing after each.
  • Under local gunicorn: the integration suite passes, the Deutsch-Jozsa, Bernstein-Vazirani and SAT --baseurl self-tests pass, and an HTTPS request with the new certifi bundle succeeds.
  • Docker image built from this branch: the container reports healthy and the integration suite passes (6 tests).
  • The full rbs ci pipeline was not run locally (no devcontainer); this PR's CI run covers that.

Note: the image doesn't follow the lock file

The Dockerfile installs the wheel with uv pip install, which resolves runtime dependencies fresh from PyPI and ignores uv.lock. So the audit gate checks the lock file, but the image gets whatever versions are newest at build time. It already has the patched werkzeug, urllib3 and certifi, but the next vulnerable release could ship in the image while the lock stays clean. Installing with uv sync --frozen --no-dev would make the image match the lock. Left for a separate PR.

Merge order

#26 (maxcut endpoint) is failing the same gate. Once this merges, #26 will be rebased onto main and its uv.lock re-locked.

🤖 Generated with Claude Code

Clear the 19 pip-audit findings that fail the rbs audit gate by
upgrading the affected packages in uv.lock:

- werkzeug 3.1.8 -> 3.1.9 (via Flask)
- urllib3 2.7.0 -> 2.8.0 (via requests)
- certifi 2026.6.17 -> 2026.10.23 (via requests)
- black 26.5.1 -> 26.10.1 (dev)
- pip 26.1.2 -> 26.3 (dev, via pip-audit)
- filelock 3.29.5 -> 4.2.11 (dev, via pip-audit)
- msgpack 1.2.1 -> 1.2.4 (dev, via pip-audit)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Redux Build System — CI Report

uv · commit 8e77611

Operation Status Summary Time
audit ✅ no known vulnerabilities 7.6s
format-check ✅ all files formatted 0.6s
lint ✅ 0 issues 0.0s
typecheck ⏭️ not implemented —
unit-test · 3.12 ✅ 65 passed · coverage 86% 107.5s
unit-test · 3.13 ✅ 65 passed · coverage 86% 103.6s
build ✅ built local/quantumsolver:ci · 581MB 15.8s
integration-test ✅ /health ready · 6 passed 7.8s
push ⏭️ only on push to main —

Overall: ✅ 7 passed · 0 failed · 2 skipped

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

@Trosper3 Trosper3 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My name is Michael Trosper and I approve this message.

In all seriousness, this looks good. I saw some related vulnerabilities get corrected on some of the other repositories, so this makes sense.

@Trosper3
Trosper3 merged commit 6370765 into main Nov 17, 2026
4 checks passed
@Trosper3
Trosper3 deleted the chore/pip-audit-upgrades branch November 17, 2026 17:00
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.

3 participants