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!

    ProGet 5.0.x - Semantic versioning

    Scheduled Pinned Locked Moved Support
    progetupdatenuget
    5 Posts 2 Posters 47 Views
    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.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Hi,
      We are currently using ProGet 5.0.8 in QuirksMode, so my question is if we migrate our feed what does this mean to us (what do we have to consider, what do we have to do --> so we can plan the effort).
      What consequences do this have:
      "In ProGet 5.0, new NuGet feeds now use a more sophisticated versioning scheme that accommodates semantic versioning 2.0 rules for pre-release version strings."

      Thx in advance

      Product: ProGet
      Version: 5.0.8

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

        Have you seen the Legacy (Quirks) NuGet Feeds documentation?

        If so, can you add a more specific question? I think it provides some guidance on what it does, and what to consider.

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

          Hi, Yes I have read the documentation and the only thing I'm not quite sure is, as already posted in my initial question:
          "In ProGet 5.0, new NuGet feeds now use a more sophisticated versioning scheme that accommodates semantic versioning 2.0 rules for pre-release version strings."

          Does this only mean semantic versioning 2.0 rules for pre-release are enforced?
          Or this this also mean semantic versioning 2.0 rules for non pre-release packages are enforced?

          At the moment our company NuGet packages only using the first two digits from the version (like 2.3.0.0) --> therefore we have to reuse the number (I know we shouldn't do that and we are already working on the migration), will this still be possible?

          br

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

            Basically this is changing the way the pre-release versioning (like 1.2.0-2.3.4) works. Now, 2.3.4 is sorted, and isn't an arbitrary string.

            The NuGet client is already "normalizing" versions, and if you have a package like "2.3" then it will be sent as "2.3.0.0" to the client.

            If you run the migration tool, you'll be able to see if any issues come up, and it will be rolled back.

            1 Reply Last reply Reply Quote 0
            • S Offline
              sowthriganth.s_6450
              last edited by

              Hi,

              Please refer the below blog. You may have an idea on Semantic Versioning.
              https://www.meritedin.com/robust-api.html

              Please don't forget to take a look on the videos listed on their playlist.

              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