Skip to content

fix(deps): langgraph-checkpoint-sqlite 3.1.0 -> 3.1.1 (PYSEC-2026-3636) - #869

Merged
rlagowski merged 1 commit into
developfrom
fix/deps-langgraph-checkpoint-sqlite
Aug 11, 2026
Merged

fix(deps): langgraph-checkpoint-sqlite 3.1.0 -> 3.1.1 (PYSEC-2026-3636)#869
rlagowski merged 1 commit into
developfrom
fix/deps-langgraph-checkpoint-sqlite

Conversation

@rafeekpro

Copy link
Copy Markdown
Collaborator

CI run #1734 failed pip-audit on branch chore/sync-pr-review-gate (#868) — a PR that
carries a two-line gate sync and nothing else. The advisory landed after the last green run
on develop, so an unrelated change is what surfaced it.

Name                        Version ID              Fix Versions
langgraph-checkpoint-sqlite 3.1.0   PYSEC-2026-3636 3.1.1

The fix, and why the floor goes where it goes

Same shape and same remedy as the postgres sibling in 8f3db0e. The direct requirement in
apps/engine is langgraph-checkpoint-sqlite>=2.0.0, which resolved happily to the
vulnerable 3.1.0 — so the floor goes in the constraints list beside the other advisory
floors
, not tightened at the requirement. One list, read in one place, when the next
advisory lands. That is the convention langgraph-checkpoint / langsmith / msgpack
already established there.

Verification

Run with the exact command CI runs, after uv sync --all-packages --frozen:

$ uv run pip-audit --ignore-vuln PYSEC-2025-183
No known vulnerabilities found

The two skipped rows (code-review-council, dap-database) are the workspace's own
packages — local, not on PyPI, skipped as designed.

uv.lock: langgraph-checkpoint-sqlite 3.1.0 -> 3.1.1, no other resolution moved.

Unblocks #868 (the gate sync from pr-review-gate#329).

🤖 Generated with Claude Code

CI run #1734 failed pip-audit on branch chore/sync-pr-review-gate (#868), which
carries a two-line gate sync and nothing else — the advisory landed after the
last green run on develop and now blocks an unrelated PR.

Same shape and same remedy as the postgres sibling in 8f3db0e. The direct
requirement in apps/engine is `langgraph-checkpoint-sqlite>=2.0.0`, which
resolved happily to the vulnerable 3.1.0, so the floor goes in the `constraints`
list beside the other advisory floors rather than being tightened at the
requirement — one list, read in one place, when the next advisory lands. That is
the convention the langgraph-checkpoint / langsmith / msgpack entries already
established.

Verified with the exact command CI runs (`uv run pip-audit --ignore-vuln
PYSEC-2025-183`) after `uv sync --all-packages --frozen`: "No known
vulnerabilities found". The two skipped rows (code-review-council, dap-database)
are the workspace's own packages — local, not on PyPI, skipped as designed.

uv.lock: langgraph-checkpoint-sqlite 3.1.0 -> 3.1.1, no other resolution moved.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@rlagowski
rlagowski merged commit e7c2568 into develop Aug 11, 2026
17 checks passed
@rlagowski
rlagowski deleted the fix/deps-langgraph-checkpoint-sqlite branch August 11, 2026 19:38
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.

2 participants