Change to have the requirements-dev.txt file generated using pip-compile. This allows for painless upgrading to the latest versions dependent on restrictions laid out in the requirements.in file for compatible, above, lower, or pinned versions as well as dependencies between libraries. It also explicitly states which libraries are being brought in and used by our list of required ones and pins the version for all in the requirements-dev.txt file so that developers are working off of the same versions.
This file can be generated with pip-tools using the command
and has been added as a make action under make pydep-upgrade.
This process flow will not upgrade the requirements.txt versions automatically without someone manually running the make operation where the new versions would then be committed to source control for use by consumers of the repo.
Change to have the requirements-dev.txt file generated using
pip-compile. This allows for painless upgrading to the latest versions dependent on restrictions laid out in therequirements.infile for compatible, above, lower, or pinned versions as well as dependencies between libraries. It also explicitly states which libraries are being brought in and used by our list of required ones and pins the version for all in therequirements-dev.txtfile so that developers are working off of the same versions.This file can be generated with
pip-toolsusing the commandand has been added as a make action under
make pydep-upgrade.This process flow will not upgrade the
requirements.txtversions automatically without someone manually running the make operation where the new versions would then be committed to source control for use by consumers of the repo.make ci-readyhas completed successfully