<![CDATA[ProGet - Yanked package behaviour]]>Hi,

Could you please explain the behaviour around how ProGet handles yanked packages for public feeds?

Scenarios:

  1. The package is yet to be downloaded to ProGet, and the user attempts to download a janked version. I'm sure ProGet will block the download in this case.

  2. The package has been downloaded to ProGet, and is then yanked from the remote. Will ProGet update it's feed index to mark it is yanked and also remove any local files that have been previous downloaded?

This is mainly aimed at PyPi - but I guess the same behaviour would apply to other feed types.

Thanks!
-Ashley

]]>https://forums.inedo.com/topic/5802/proget-yanked-package-behaviourRSS for NodeWed, 29 Jul 2026 01:31:07 GMTTue, 28 Jul 2026 10:04:09 GMT60<![CDATA[Reply to ProGet - Yanked package behaviour on Tue, 28 Jul 2026 13:54:04 GMT]]>HI @ashley,

A package's unlisted state (i.e. "yanked" in PyPi or Ruby) is server-side metadata, similar to download count. That means, once a package moves servers (i.e. from pypi.com to ProGet), that metadata is owned and maintained by the new server. When a package is cached/pulled into ProGet, that state is copied from the remote server.

An unlisted/yanked package may still be downloaded and consumed, and it's up to the client to determine how to use (or not use) packages with that status. ProGet simply displays an "hidden icon" next to unlisted packages. Visual Studio does not display them at all. I would imagine pip doesn't consider them in dependency resolution and might give a warning if consumed directly.

That said, the OSS Metadata Updating & Caching will routinely sync Listed and Deprecated statuses, but it comes at an obvious performance cost. Or you can use retention policies to more aggressively delete cached packages.

Hope that helps.

--Dean

]]>https://forums.inedo.com/post/19889https://forums.inedo.com/post/19889Tue, 28 Jul 2026 13:54:04 GMT