Hi @Michael-poutre_3915,
It's strange indeed. I wonder if it's related to a locally cached version you have?
I can't seem to find any documentation, but I believe PowerShell expects to only receive the latest version available unless a specific version is specified(This is based on the fact that if more than one package is found, it errors). Looking further into ProGet returning two results, we see that it is returning the latest non local version as well as the latest local version. I think if ProGet were configured to only return the latest version that that would work better
Behind the scenes, PowerShell is calling the FindPackagesById() NuGet API method which is supposed to return all versions.
You should see almost identical results to:
https://www.powershellgallery.com/api/v2/FindPackagesById()?id='ExchangeOnlineManagement'
https://proget.company.com/nuget/PowerShell/FindPackagesById()?id='ExchangeOnlineManagement'
You'll notice the same with InvokeBuild as well; all versions are returned from the API, as expected. So this is why I think there's multiple repositories (a local one?) or caching, or some other thing with the client. I know you can install a module locally, in powershell, by copying the module file to a directory?
Sorry I'm not really good with degubbing the PowerShellGet client, but hopefully we can figure it out....
Cheers,
Alana