Skip to content

chore: sync AI review gate (pr-review-gate) - #868

Merged
rlagowski merged 2 commits into
developfrom
chore/sync-pr-review-gate
Aug 11, 2026
Merged

chore: sync AI review gate (pr-review-gate)#868
rlagowski merged 2 commits into
developfrom
chore/sync-pr-review-gate

Conversation

@Dixter999

Copy link
Copy Markdown
Collaborator

Automated sync of the unified AI review gate from lagowski/pr-review-gate.

Do not edit the workflow here — change it centrally in pr-review-gate and redeploy. Found a gate bug? Open an issue there.

Automated deploy. Do not edit the gate here — change it in lagowski/pr-review-gate and redeploy.
rlagowski pushed a commit that referenced this pull request Aug 11, 2026
…6) (#869)

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 576c1b5 into develop Aug 11, 2026
17 checks passed
@rlagowski
rlagowski deleted the chore/sync-pr-review-gate branch August 11, 2026 19:42
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