Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-24868

Group does not export semver2 endpoints `RegistrationsBaseUrl/Versioned` when used as NuGet V3

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.27.0
    • Fix Version/s: 3.28.0
    • Component/s: NuGet
    • Labels:
      None

      Description

      When use NuGet v3, unlike nuget.org-proxy, nuget-group only exports  `RegistrationsBaseUrl/3.6.0` but not  `RegistrationsBaseUrl/Versioned` as semver2 endpoints. But seems for some unknown reason, nuget client only checks `RegistrationsBaseUrl/Versioned` but not `RegistrationsBaseUrl/3.6.0`, so it's not possible to get only semver2 only packages with nuget-group.

      https://github.com/NuGet/NuGet.Client/blob/e08358296db5bfa6f7f32d6f4ec8de288f3b0388/src/NuGet.Core/NuGet.Protocol/ServiceTypes.cs

      https://github.com/NuGet/Home/wiki/Semver-2.0.0-Protocol

       

       

      For something like `Microsoft.EntityFrameworkCore`, it's only possible to see 3.1.x, but not 5.0.0-preview.7.20365.15 in nuget-group, and nuget.org-proxy works well.

      https://www.nuget.org/packages/Microsoft.EntityFrameworkCore/5.0.0-preview.7.20365.15

       

      And also for nuget-hosted.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jhill Joshua Hill
              Reporter:
              yyjdelete SilverFox
              Last Updated By:
              Michael Bucher
              Team:
              NXRM - Trinity
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title

                    PagerDuty