Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
SemVer2.0 packages from nuget.org are not visible
-
Hello,
it seems that nuget.org v2 feed does not work with SemVer 2.0 packages, so these packages don't appear in ProGet when connected to nuget.org. At https://inedo.com/support/documentation/proget/feeds/nuget, you say that "there is no need or benefit to having ProGet support the JSON-LD protocol" and that "it is on our 2019 roadmap to implement this API". Since ProGet 5.0 is supposed to support SemVer 2.0, is there a way to make this scenario work?
Product: ProGet
Version: 5.0.12
-
The "protocol/API" (ODATA vs JSON-LD) really doesn't make an impact on this.
In ProGet v5, NuGet feeds to in fact support SemVer2 packages. If you're finding errors, then you may have a legacy feed: please refer Legacy (Quirks) NuGet Feeds for how to migrate. Otherwise, if you have specific error cases that we might be able to try to reproduce, please let us know it.
-
Alana, the issue is not with ProGet, it is with NuGet.org not exposing SemVer 2.0.0 packages over the v2 feed.
We need ProGet's connectors to speak JSON-LD so that we don't miss out on upstream versions hosted on NuGet.org. A good example is XUnit. My ProGet instance tells me the latest version is 2.3.1, but there are actually two versions after that available at https://www.nuget.org/packages/xunit/2.4.0-beta.2.build4010
-
Exactly. https://www.nuget.org/packages/NuGet.Packaging/4.7.0 is another example.
I made sure we have everything upgraded including the feed, but as Jim says, the problem is on the side of the connector to NuGet.org.
(To fix this issue, you might actually use the libraries in the NuGet.* packages, so you don't need to reverse-engineer the JSON-LD protocol.)
-
Hello Tony,
I've filed PG-1294 to fix this. As a workaround, you can access the package directly by version number even without this fix.
-
That fix isn't in 5.0.13. Any idea when it will be released?
-
unfortunately this bug fix just missed the cut.
But we will ship it in the next maintenance release, likely in a couple weeks. It's not scheduled yet.
