Hi @infrastrcture_6303 , We've had one other user report this, and unfortunately it's a bit complicated behind the scenes. ProGet 6 allowed npm packages to be uploaded without a @ in the scope, which meant that if you used a non-npm client (your own script, etc), you could have "bad data" in the database. We did not anticipate this data when doing the ProGet 2023 datamigration, so the bad data was brought over. We don't have a means of fixing it, and it would take a nontrivial amount of time to do that - so as a free user we can't really put in that time. We do plan on a cleanup task ina few months that will take care of this automatically. If you're comfortable with SQL, you may be able to fix it yourself (that's what the other user did), and it invovles a figuring out some queries around the PackageNameIds table. Another alternative is to setup a new instance of ProGet 2024 and then just import the packages from disk. Thanks, Alana

Hi @jfullmer_7346 , I was able to reproduce this, and we will fix it in an upcoming maintenance release (PG-2920). This came from a regression in 2024.28, with some other NuGet feed changes. Cheers, Alana

Hi @procha_8465 , I'm afraid we'll need a bit more information here to help you. There are a lot of changes between ProGet 5.2 and ProGet 2024 and between older/newer versions of the npm client. If you can put together a reproduction case, ideally on a new instance of ProGet 2024, that'll help us determine what you're trying to do and how to help. -- Dean

Hi @f-medini_8369, Here is our documentation on how to use Prometheus: https://docs.inedo.com/docs/installation/logging/installation-prometheus -- Dean

Hi @pratik-kumar_8939 , ProGet does not require two different feeds for this, and we would generally recommend putting them in the same feed. If you wish to have the artifacts intwo different feeds, then you can just create different feeds and name them how you'd like. Thanks, Alana

Hi @simon-marriott_1201, If you haven't seen it already, I'd check out How Files and Packages Work in ProGet for Artifactory Users. Long story short is, you should consider a more modern approach than the Maven-based file/folder that Artifactory uses. Many have found a lot of success with Universal Feeds & Packages. We don't maintain a TeamCity plugin, but it's really easy to create, publish, deploy packages using the pgutil command line (i.e. pgutil upack create); see HOWTO: Create Universal Packages Hope that helps! -- Dean

That's a display issue in pgutil. It's not supposed to show the build number as part of the version at all, so we'll fix that. Note that we do include the build as part of the tag, but the actual release title on GitHub is just 2.1.1, 2.0.6, etc. Thanks for reporting this!

@atripp Thanks so much for the information

@rhessinger I added the requested info to the opened ticket. Best Regards, Pedro

Hi @dean-houston, thanks for the reply. That solved the problem. In addition I finally had to configure my Visual Studion correctly by adding /v3/index.json to the feed address. I had missed this for quite some time, unfortunately. Now everything is running fine. Best regards Uwe

Hi Alana. Thanks for your feedback. I will try it like that. Best regards Paddy

@jipianu_mihnea_1277 said in Creating Users with Native API: ant to use the Native API to create users and groups, but I do not know how to generate the password because I am unaware of th Thanks for the shout-out @atripp! Yes, you can do Set-ProGetUserPassword -Credential (Get-Credential) and supply the username of the account you with to set the password, as well as the new password. The New-ProGetUser function will do this internally for you when you pass in the credential object that function expects. If you run into trouble, please do file an issue so I can try to fix it!

@atripp , Guess you are right. thank you.

@layfield_8963 great news, that was a really strange error. The UI upload uses some kind of chunking and file appending, so it sounds like that was it.

Thanks for the reply, we on our end have to take a discussion and see if there is a budget increase option or if we just throttle traffic.

Hi @enrico-proget_8830, So we have fixed multiple issues with npm, specifically the npm connectors in the versions since you installed. I think upgrading to ProGet 2025.26 should resolve your issue with the ECONNRESET issue. Could you update to 2025.26 and rerun your test and let us know if you are still seeing the issue? Here is a link to the change list since your version of ProGet: https://my.inedo.com/downloads/upgrade?product=ProGet&fromVersion=2024.22 Thanks, Rich

@dan-brown_0128 thanks for clarifying 2500 is a lot more than I'm thinking... I was envisioning a handful of frequently-updated / highly-trusted packages (like AWSSDK, ). I think the UI would struggle a bit. Thinking about this further... a blanket "all future versions are OK" policy seems like it will cause more problems than benefits. That's a lot of decision-making burden to shift to developers, and they're just going to hit "update" the moment they're prompted. Best case scenario, that update delivers Zero Business Value... but there's a chance it'll introduce a regression, etc. I'd really need to study the data before recommending a practice like this (let adding a supported usecase for it) I'd be open to some sort of "automatic approval" feature, but I'd want to see some other factors in there, other than just "name matches X". As it stands, "package approval/promotion" isn't very widely used as it's solving a problem most organizations don't believe they have. Instead they drop $300K+ for Clownstrike or another security tool and believe it just "does everything for them". At that price, how could it not! So I think it's best to pin this for a bit. It's still a pretty "frontier" discussion/feature, and I don't want to "invent" something that's not going to get a lot of widespread use.

@stevedennis I understand not wanting to go in blind on something so low-level. For what it is worth, the monkey-patch I applied has been stable, so far, in my lab environment. Let me know if you need me to test a build, prior to Otter 2025.

Hi Dean, Setting RaftItemType_Code = 7 in this instance worked for me. Appreciate the list of valid types. Thanks for all of your help! Scott