-
Notifications
You must be signed in to change notification settings - Fork 108
Chores #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chores #159
Conversation
…iles Co-authored-by: sanchitram <sanchitram@gmail.com>
add dependencies / dependents count to /projects
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR performs maintenance tasks to improve the project's dependency management and Docker build process. The changes focus on switching from psycopg2 to psycopg2-binary for PostgreSQL connectivity and standardizing Docker builds to use uv for faster package installation.
- Replace
psycopg2withpsycopg2-binaryfor better deployment compatibility - Migrate package manager Docker images from pip to uv for consistent build tooling
- Fix documentation and database initialization script issues
Reviewed Changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| pyproject.toml | Updates psycopg2 dependency to use binary version with pinned version |
| core/requirements.txt | Reflects the psycopg2-binary dependency change from pyproject.toml |
| package_managers/*/Dockerfile | Migrates from python:3.11 base image to uv-enabled image with uv pip install |
| alembic/init-script.sql | Enables pg_trgm extension instead of commented pg_bigm |
| alembic/Dockerfile | Adds TODO comment about psql dependency requirement |
| README.md | Corrects typo in dependency group name from "indexer" to "indexers" |
| "idna>=3.10", | ||
| "permalint>=0.1.15", | ||
| "psycopg2>=2.9.10", | ||
| "psycopg2-binary==2.9.10", |
Copilot
AI
Aug 11, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing from a range constraint (>=2.9.10) to an exact pin (==2.9.10) removes flexibility for patch updates that might contain security fixes. Consider using a more flexible constraint like ~=2.9.10 to allow patch-level updates.
| "psycopg2-binary==2.9.10", | |
| "psycopg2-binary~=2.9.10", |
There are some redundant merge requests in here, but:
psycopg2-binaryinstead ofpsycopg2uvto build the docker images for the indexers as well, similar to how we do it for alembic