Installing requirements-dev.txt results in a reinstall of since updated packages

[pamelafox]

Notice reinstall:

Installing collected packages: psycopg2-binary, django, google-auth, azure-core
  Attempting uninstall: psycopg2-binary
    Found existing installation: psycopg2-binary 2.9.5
    Uninstalling psycopg2-binary-2.9.5:
      Successfully uninstalled psycopg2-binary-2.9.5
  Attempting uninstall: django
    Found existing installation: Django 4.1.7
    Uninstalling Django-4.1.7:
      Successfully uninstalled Django-4.1.7
  Attempting uninstall: google-auth
    Found existing installation: google-auth 2.17.0
    Uninstalling google-auth-2.17.0:
      Successfully uninstalled google-auth-2.17.0
  Attempting uninstall: azure-core
    Found existing installation: azure-core 1.26.3
    Uninstalling azure-core-1.26.3:
      Successfully uninstalled azure-core-1.26.3
Successfully installed azure-core-1.26.4 django-4.2 google-auth-2.17.2 psycopg2-binary-2.9.6

I believe this is due to version mismatch. I assume one of the files should be re-generated but not sure which.

[pamelafox]

@kjaymiller I'm not sure workflow for re-generating requirements files to make sure they match, but I believe that's whats necessary here. It's not a huge deal that things got uninstalled, but it'd be a nicer dev experience if they weren't (and faster).

[kjaymiller]

I think currently it's manual, however I do believe we have dependabot that should manage that should manage that.

[pamelafox]

Not currently relevant, right, as we moved from pip-tools to unpinned .in?

[kjaymiller]

correct however if we're using requirements.in instead of requirements.txt we can manually manage the requirements.txt.