@jjones

Thanks for the update. In the meantime, especially if this is going to be a while before a fix is introduced, is there a supported workaround? Perhaps using the stored procedure in the database?

Thanks,
Chris

In the last few versions of ProGet, I have been unable to use the NuGetPackages_SetListed api endpoint. The below is an example call in PowerShell:

$feed_Id = 5
$package_Id = 'Package.Id.Hidden'
$package_Version = '0.1.0.12-rc'
$listedIndicator = 'false'
$unlistUri = "$baseUri/api/json/NuGetPackages_SetListed?Feed_Id=$($feed_Id)&Package_Id=$($package_Id)&Version_Text=$($package_Version)&Listed_Indicator=$($listedIndicator)"
Write-Output $unlistUri
$r = Invoke-WebRequest -Uri $unlistUri -Method Post -Headers $reqheaders -UseBasicParsing

Running the above (with appropriate headers and access) previously unlisted or listed a package, but it no longer works. It returns a 200 with no content, which is expected, but the package remains in it's previous state. I confirmed in the web ui and the database that the package is still listed.