Skip to content

chore(deps): drop redundant psycopg2-binary + pgvector direct pins (via alpha-engine-lib[rag])#276

Merged
cipher813 merged 1 commit into
mainfrom
chore/drop-redundant-psycopg2-pgvector
May 20, 2026
Merged

chore(deps): drop redundant psycopg2-binary + pgvector direct pins (via alpha-engine-lib[rag])#276
cipher813 merged 1 commit into
mainfrom
chore/drop-redundant-psycopg2-pgvector

Conversation

@cipher813
Copy link
Copy Markdown
Owner

Summary

Drops the duplicate direct pins on `psycopg2-binary>=2.9` and `pgvector>=0.2` in `requirements.txt` — both are now supplied by the `alpha-engine-lib[rag]` extra (added in lib v0.3.0, now pinned at v0.20.0). The direct pins were the explicit "kept for now to avoid breaking pinning during the migration" carve-out that the L615 ROADMAP entry tracked; gate cleared with >2 weeks of soak.

Verification

  • `alpha-engine-lib[rag]` extra at `pyproject.toml:27-29` declares the same lower bounds (`psycopg2-binary>=2.9` / `pgvector>=0.2`).
  • `python -c "import psycopg2; import pgvector"` succeeds after the drop (psycopg2 resolves to 2.9.11 via the lib extra).
  • Full suite: 1401 passed / 1 skipped — no regression.

Closes the L615 P3 → P2 promotion from the 2026-05-20 P3 curation pass.

Test plan

  • Suite green locally (1401 / 1 skipped)
  • Next Saturday SF (5/23) DataPhase1 + DataPhase2 spot launches with the slim image and `psycopg2-binary` / `pgvector` still resolve via the lib extra.

🤖 Generated with Claude Code

…ow via alpha-engine-lib[rag])

These pins were added direct in 2026-05-03 alongside the
alpha-engine-lib v0.3.0 migration that consolidated them into the
new `[rag]` extra. The original entry kept them direct "to avoid
breaking pinning during the migration." The lib is now pinned at
v0.20.0 (>2 weeks of Saturday-SF + weekday-SF soak with the
extra-managed deps), so the duplicate direct pins are dead weight
and a dual-pin drift surface.

Verification:
- `alpha-engine-lib[rag]` extra at `pyproject.toml:27-29` declares
  `psycopg2-binary>=2.9` + `pgvector>=0.2` — identical lower bounds.
- `python -c "import psycopg2; import pgvector"` succeeds after the
  drop (psycopg2 2.9.11 resolved via lib).
- Full suite: 1401 passed / 1 skipped (no regression).

Closes the L615 P3 → P2 promotion from the 2026-05-20 P3 curation
pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@cipher813 cipher813 merged commit 2fd8949 into main May 20, 2026
1 check passed
@cipher813 cipher813 deleted the chore/drop-redundant-psycopg2-pgvector branch May 20, 2026 17:33
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.

1 participant