This still requires testing, but we suspect that if we set the dependency requirements to a minimum version using the >= syntax, that may force a re-install / upgrade of the dependencies to the minimum required version if that dependency already exists in the environment of a user. We need to confirm this, but if we confirm this to be the case, we should publish a version 3.0.1 that contains the updated requirements.txt.
This still requires testing, but we suspect that if we set the dependency requirements to a minimum version using the >= syntax, that may force a re-install / upgrade of the dependencies to the minimum required version if that dependency already exists in the environment of a user. We need to confirm this, but if we confirm this to be the case, we should publish a version 3.0.1 that contains the updated requirements.txt.
This was inspired by this issue.