Apply pending backend dependency bumps with regenerated lockfiles - #294
Merged
Merged
Conversation
Supersedes the four open dependabot PRs for the backend: sqlalchemy 2.0.51 -> 2.0.52 (#286) litellm 1.94.1 -> 1.96.2 (#287) uvicorn 0.52.0 -> 0.52.3 (#288) alembic 1.18.5 -> 1.19.1 (#289) Each of those PRs edits one line of pyproject.toml and stops there. Because CI installs `--require-hashes` from the lock and then `pip install --no-deps -e .`, pyproject's pins are never enforced — so merging them as written would change the declared versions without changing a single installed package. This applies the same four bumps and regenerates both lockfiles, so they actually take effect. No transitive versions moved beyond the four and their own pins. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KqXjgMRArAxubgd5f5UYgC
d3mocide
marked this pull request as ready for review
September 16, 2026 15:20
This was referenced Sep 16, 2026
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
2 participants
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.
Re-targets the work from #293 at
maindirectly.Why this PR exists
#293 was stacked on #292's branch (
claude/backend-dep-audit-fixes) with the expectation that GitHub would auto-retarget it tomainonce #292 merged. That only happens when the base branch is deleted on merge — it wasn't, so #293 ended up merging its commit into the now-staleclaude/backend-dep-audit-fixesbranch after that branch had already been folded intomain. GitHub shows #293 as "Merged", but the commit never reachedmain.mainis still on the pre-bump versions.This PR carries that same commit (
d427bbe, unchanged) withmainas the base, so it actually lands this time.What it does
Supersedes the four open backend dependabot PRs, applying the same bumps with regenerated lockfiles:
Each of those PRs only changes
backend/pyproject.tomlwith no lockfile regeneration, so merging them as-is would change declared versions without changing installed packages (and would now fail the lockfile-drift check added in #292).No transitive dependency changed beyond these four.
Testing
Carried over from #293 (no code changes since, only the merge base):
pip-audit— No known vulnerabilities foundruff check .— All checks passedmypy luma --ignore-missing-imports— Success, 78 source filespytest -x -q— 201 passedpip-compilere-runWorth a look before merging: the
Migrations — apply & checkCI job needs a live TimescaleDB, which I can't exercise locally — that job on this PR is the real check for the alembic 1.18 → 1.19 bump.Once this is green, #286–#289 can be closed as superseded.
🤖 Generated with Claude Code
https://claude.ai/code/session_013NXCVFjazLiKnd8mCCCj7r
Generated by Claude Code