-
Notifications
You must be signed in to change notification settings - Fork 172
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
fix: use .txt files inside .in files to ensure consistency across environments #4556
base: master
Are you sure you want to change the base?
Conversation
04c4142
to
0ab0fb1
Compare
@@ -0,0 +1,1029 @@ | |||
# |
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.
If test.txt did not exist before, is it being used anywhere in CI flow? or is everything under local.txt?
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.
I don't think it's being used anywhere. If it were, things would have broken
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.
Hmmm, strange.
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.
Should we not update test/CI to use test.txt? I mean the purpose of having the separate dependencies was to be able to use environment-specific dependencies.
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.
Updated the tests to use test.txt
d573bf8
to
7a777fb
Compare
PROD-3793
If we include
.in
files as requirements (instead of.txt
files), there is a possibility that different envs (dev, prod, local, test etc.) may get different versions of the same package. An example is the attrs package in our repository. The local env has version 21.4.0 whereas the prod env has version 25.1.0This PR is an attempt to ensure that package versions are consistent across environments.
It might be helpful to review the commits separately.