jrasch

I would like to add that this is affecting our ProGet product, which sends the `semVerLevel` query string argument as per the [NuGet server spec](https://github.com/NuGet/Home/wiki/SemVer2-support-for-nuget.org-(server-side)#backwards-compatibility). ProGet relies on the `IsLatestVersion`...

This appears to be fixed now.

My mistake, there was another version of that package released so the `IsAbsoluteLatestVersion` property became `true`, but `IsLatestVersion` still does not work when that is used as the filter: https://www.powershellgallery.com/api/v2/FindPackagesById()?$filter=IsLatestVersion&id=%27WindowsCompatibility%27&semVerLevel=2.0.0

Here is an example of a package that shows `false` for `IsLatestVersion` and `IsAbsoluteLatestVersion` even though there's only a single version: https://www.powershellgallery.com/api/v2/FindPackagesById()?$filter=IsLatestVersion&id=%27xDisk%27&semVerLevel=2.0.0 ``` falsefalsefalse ``` The values for those elements...