powershell force module version dependency in module

Question

I recently discovered an issue with the powershellget module that seems to be resolved in the beta versions of that module. When I run powershell, it automatically seems to load