Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. benjamin.soddy_9591
    3. Posts
    B
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by benjamin.soddy_9591

    • RE: Marking packages as deprecated

      I am extraordinarily apologetic for resurrecting this, but it seemed more correct than creating a new, duplicate topic.

      My organization has been and is in the process of making a large number of acquisitions. These companies have their own disparate systems and processes. However, a unifying aspect of the .NET companies is their use of the NuGet API and .NET SDK. Using these channels for deprecations and vulnerabilities via dotnet list package --vulnerable and dotnet list package --outdated is highly desirable. In no uncertain terms, dependencies distributed and shared by these teams are have few differences when compared with dependencies from NuGet.org. In fact, some dependencies shared amongst these teams are distributed via NuGet.org as public packages.

      It is far more direct to use established standards which work with NuGet.org feeds, than to add an additional burden of knowledge. At the moment, the only recourse is to create a NuGet.org organization and change our distribution model.

      posted in Support
      B
      benjamin.soddy_9591
    • Marking packages as deprecated

      How can I mark packages as deprecated? Package deprecations are a defined component of the NuGet Server API.

      I am currently managing projects using the dotnet CLI's project package commands. With this I am able to create deprecation reports for projects with dependencies on deprecated nuget.org packages. However I am unable to do so with any packages derived from a ProGet server source.

      posted in Support
      B
      benjamin.soddy_9591
    • 1 / 1