Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/python/requirements.txt
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
google-adk
google-adk==1.17.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Pinning the google-adk dependency is a great step towards ensuring reproducible builds. However, other direct dependencies in this file (such as openai, pydantic, langchain, etc.) remain unpinned.

This practice can lead to non-reproducible builds, where different environments (developer machines, CI/CD, production) could install different package versions, potentially causing unexpected behavior or breakages.

To guarantee build stability, I strongly recommend pinning all dependencies in this file to specific, known-good versions. For example:

openai==x.y.z
pydantic[email]==x.y.z
langchain==x.y.z
# ... and so on for all dependencies

For more robust dependency management, consider using a tool like pip-tools. This allows you to manage your primary dependencies in a requirements.in file and automatically generate a fully-pinned requirements.txt that includes all transitive dependencies.

openai
pydantic[email]
langchain
Expand Down
Loading