@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.

@jimbobmcgee thank you again for the very detailed analysis; we will get this fixed via OT-515, it's most an easy encoding to add

Hi @mail_6495 , Looks like this was a regression with API Key Authentication; the uploader control improperly required an API key. This will be fixed in PG-2104 on this Friday's maintenance key update. Cheers, Alana

Hi, Thanks for reporting this. We've now fixed this internally as PG-2105 - it will be included in this week's 6.0.9 release, scheduled for Friday. -Greg

That one works, thanks!

I fixed this incidentally in this commit: https://github.com/Inedo/inedox-git/commit/325562db2ea5996a1dc559f5997dca49cc9452df The fix is available as of v1.3.1 of the Git(Hub|Lab)? extensions :)

Unfortunately this was a regression present in 5.1.19, but has since been fixed in 5.1.20 which was released earlier today.

Thanks for the update; due to its severity we put out an emergency maintenance release to fix this.

This will be addressed in next maintenance release as PG-1294 . As a workaround, you can access the package directly by version number even without this fix.

Hello Rob, I've released version 1.0.1 of the TeamCity extension, which should fix this (or at least give a more sensible error message). It should be available in /administration/extensions.

Hello; thanks for the report, this has been filed as PG-1229

As a followup, support for the Portable PDB format in the symbol/source server has since been added to ProGet.

Hi Tod Thanks for the fast response. Since i am not relying on the statistics of Proget i have solved the issue with a bit of work. Created new feed that uses new standards setup custom feedpath and droppackage path for bulk import on the server i located that packages on the filesystem and dumped into the appropiate bulk import folder. wait a minute or two and the new feed has all the packages. Rename feeds so the new one has the name of the old deprecated. It is a workaround but it works but again - you loose statistics. Symbols and Source seem to survive :-D

Hello Julien, I've filed this as PG-1147 and a fix should be coming in the next version of ProGet.

Thanks for the clarification; I was able to repro this and logged a bug report (BM-2371). It will be addressed in a future maintence release.

Thanks for the bug report. We'll investigate and get a fix in the next release. We probably will also change the group syntax in dependencies to use a / instead of a colon, so you could just specify: "Root" (or "group/Root", etc). Of course, we would retain compatibility with the : syntax as well, but this would make things less ambiguous.

I think we've identified this and will fix this in the next maintenance; it only impacts the free version, but you can workaround as you've noted.

It's hard to say why there's a discrepancy, but you can just re-index the entire connector. Just run the "FullNpmConnectorIndex " scheduled task, accessible from the admin portal. This will take several minutes. There will be a LOT of warnings about "missing versions property". You can ignore thesethey are effectively invalid npm packages that they return anyway with the index request.

Thanks for your prompt reply. The patch script you linked certainly fixed Issue#4 for us. I think we should be fine to push forward with 4.7.3 as it looks like all the issues have now been resolved. Thanks for linking through that knowledge base article. I'll be sure to have a look through the knowledge base articles before any future upgrades.

Embarrassing, a Spanish colleague had been on the server and changed all the setting!