Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    How do I exclude pre-release nugets in the connectors?

    Scheduled Pinned Locked Moved Support
    nugetconnectorsproget
    4 Posts 2 Posters 13 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      davidroberts63
      last edited by

      Recently went from 3.8.1 to 4.8.2 and now have better connector functionality, thank you. However, we are seeing the pre-release packages show up in feeds with a nuget v2 connector. How can we filter those out? Specifically when we view a package with dependencies if the dependency has a prerelease package, that's the one we end up seeing and linking to in the web UI.

      An example:
      Serilog.Sinks.File v3.2.0 requires Serilog (>= 2.3.0)
      Serilog's latest published version is 2.5.1-dev-00890 (which we don't want to see in ProGet).
      Serilog's latest non pre-release/stable version is 2.5.0 (which IS the one we want to see in ProGet).

      An alternative behavior would be that the pre-release ones show up but everything would default to using stable/non-pre-release packages unless specifically called out to include them by the user. Same as on nuget.org.

      Product: ProGet
      Version: 4.8.2

      github/davidroberts63 ; idoforums@teapotcoder.com

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Due to technology/querying limitations of NuGet.org, we are quite limited as to what filtering options we can do. This is why many of the filters (vulnerability, licensing, etc), are simply blocked from being downloaded (but still appear in a query).

        If establishing an internal policy doesn't work, you could certainly write a package access rule using the SDK (see the whitesource extension as an example), to prevent these from being consumed.

        1 Reply Last reply Reply Quote 0
        • D Offline
          davidroberts63
          last edited by

          I will definitely look into the extension documentation. Thank you for mentioning it.

          But, you're saying this won't work?

          https://www.nuget.org/api/v2/Packages()?$filter=**IsPrerelease eq true**&$top=10

          I imagine I'm misunderstanding something you said, or there maybe something else I'm not aware of when querying nuget.org.

          github/davidroberts63 ; idoforums@teapotcoder.com

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            It certainly might... but we haven't evaluated it for performance considerations, etc. Early on, we tried implementing a much more advanced filtering system (author, versions, etc), but it really put a strain on NuGet.org and became useless, so we didn't continue on that featureset.

            This is the first request for this specific filter, and it might be simple, but we'll definitely consider it.

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation