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!
NPM feed doesn't present highest version as latest package
-
We would like to host development packages and release candidates on the same feed as our production packages, only problem is that when we update a development build with version 0.0.0 or version 1.0.0 , that version is given when you ask to install the package without version info.
We would expect the highest version released to be picked. Is there something that we do to improve this?
I don't see anything in the recent release notes that would seem to adress this issue.
Can you help with this?
Product: ProGet
Version: 4.4.1 -
The npm client does not use version number to determine the latest version. Instead, whichever package was most recently tagged "latest" is used as the latest version.
Please refer to the following npm docs for more information
-
Tagging would indeed be the solution, now it's clear how we should have been working. Thanks for the fast feedback!
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