Awesome Reviewers

In configuration files like requirements.txt, define a consistent versioning policy:

• Prefer minimum version constraints (>=) for most libraries to guarantee required behavior without freezing to a single patch/release.
• When you need reproducible installs across machines/CI, generate an exact set of transitive dependencies using a compiler/lock workflow (e.g., uv pip compile) and commit the resulting requirements.txt.
• Use exact pins (==) only for specific high-risk/critical integrations where compatibility must be enforced (then justify and revisit the pin periodically).

Example:

# Prefer minimum versions
boto3>=1.34.0
langchain_core>=0.3.0

# If compatibility requires it for a specific integration
mcp==1.2.3

Example reproducible build flow:

uv pip compile --output-file requirements.txt pyproject.toml

This prevents “works on my machine” drift, avoids breakage from unbounded upgrades, and keeps exceptions tightly scoped to the components that truly require them.

This site is open source. Improve this page.