ProGet v2025.5

In the Retention rules, if we enter a size of feed greater than 2097000mb, and then save, then we end up with a negative number displayed for the quota. I was aiming for 3TB - but i can foresee that at some point we might want to go much higher in the not too distance future.

The reason it's desirable is that although it's easy to get AD groups added, they are administered by a central department within the company, so each time we wish to add or remove somebody from a ProGet group, the change has to be requested, and this takes some time.

Other products we use such as TeamCity and Jira allow this. Also the system we used before ProGet allowed it :-)

It would be useful to allow Active Directory users to be added to built in groups, so that group management can be controlled locally within ProGet.

Proget 2025.3

With universal packages - in the usage instructions, the 'group name' gets repeated twice in the usage instructions, in all 3 tabs, upack client, cURL and PowerShell:

@phopkins_6694 - I've successfully used "delete all versions" in 2025.3 - but on an NPM feed rather than Choco. However I pressed the "Delete Package" button from your second screenshot rather than the "Delete Specific Version..." button that you have highlighted.

Hi @atripp,

One of the uses for upacks for us, is for storing binary images for things that are subsequently included into other CI builds. These are usually things are are not updated particularly frequently, and are not built by our CI system, for example an FPGA image, or perhaps some binary image provided to us by a component manufacturer.

So the process to update these packages is generally manual - we could use pgutil, but the UI seemed like a really nice feature. It's great for creating the first version of a package, but it just seems a bit awkward when adding a new version of an existing package, as you have to carefully re-enter the group and package name to match the existing package. So having a shortcut on the package page to add a new version of a package with the group and package name pre-filled would be really helpful.

ProGet 2025.3

On the Tasks / Permissions screen, sometimes (probably when there are an even number of rows in 'scope'). Due to the alternating shading, it's not possible to see where the divide should be between different task names:

A user with only 'Publish Packages' permission can't clear at least some ProTips. When they click the close icon on the ProTip, the error is displayed: "<username> is not permitted to perform the Admin_ManageFeed task for the current scope."

ProGet v2025.3 - Basic Edition

Since upgrading from 2024.36 to 2025.3 the user interface to allow universal packages to be created is no longer available for users with "Publish Package" permissions/task. Note this the default 'publish package' task - completely unmodified. Seems to apply to all feed types - but haven't extensively tested it.

2024.36:

2025.3:

I've made a bit of progress on this problem. I've now moved up to ProGet 2025.3 - and the image now does have lots of locales available (maybe they were there before, but I hadn't discovered how to enable them).

To enable specific locales it is necessary, it seems, to uncomment the appropriate lines in /etc/locale.gen, and run the locale-gen command.
It's then possible to set LC_TIME to this locale, and now when you send the date command it is formatted in the selected locale.

To achieve this i've added the following to my docker-compose.yml:

    entrypoint: sh -c "sed -i 's/# en_DK/en_DK/' /etc/locale.gen && locale-gen && /entrypoint.sh"
    environment:
      LC_TIME: "en_DK.utf8"

However - having done all that - The ProGet UI doesn't actually format the dates in the system locale of the container.

It would be handy to have a way to access the UI to create a universal package via the package's page. The package group and package name could therefore be pre-filled, to avoid having to cut and paste it, or for a mistake to be made in the name of the group or package. (same workflow as using the create package UI from the feed page)

I've just used "pgutil packages repackage" to change the versions on all my erroneously versioned packages from w.x.y.z to w.x.y-ci.z.

I was expecting only to see the newly versioned packages, but in fact i now have both versions listed - is this the intended / expected behaviour?

Also, i'm not seeing anything in the history tab to show that the package has been repackaged. But I can see the 'repackageHisory' in the upack.json.

ProGet version 2024.36 (build 5) - Trial license (Basic Edition Features)

@stevedennis - I'm migrating items from another system, and we do use 4-part version numbers (where the 4th is the build number). But we don't want it to ignore the build number part. Combining parts 3 and 4 isn't very pretty, and won't give a very good first impression of ProGet to my users if I say that that's not supported.

I'll look into going do the -ci.xxx route - I assume it will order them alphabetically rather than numerically though - so i guess i need to pad them with 0's to the maximum likely width.

I would like to change the date display format within the ProGet UI - either to British (dd/mm/yyyy) or better still ISO-8601 (yyyy-mm-dd).

I've found from an earlier thread that ProGet uses the systems locale settings - but we are using ProGet running on Docker - and there doesn't appear to be any locales available within the ProGet docker container. I've tried setting the environment variable LC_TIME, but it doesn't work - probably due to the locale i've specified not existing in the container.

Any ideas how to resolve this?

It would be really useful to have a way to get the URL of a file within a universal package. Could a extra option be added to the context menu in the file view to copy the URL? It's possible to grab it via the browser DevTools, when you press the Download menu entry, but it's not very convenient.

ProGet Free Edition - v2024.36 (build 5)

I'm having trouble using build numbers in the version of Universal Packages in Proget.
The Symantic Version spec https://semver.org/ suggests I should be able to add "+" <build> to a version number. However if i create packages with build numbers, they seem to overwrite previous packages of the same version (but different build number) - and the build number doesn't show up anywhere in the UI.

Alternatively i've tried creating packages with the version format w.x.y.z - which is not permitted through the create package UI, but PGUtil allows. This mostly works, except that the sorting doesn't work correctly when you list the packages (it works correctly for x.y.z style versions).
Even though this version convention doesn't meet the semantic version spec - it would be good it it continued to work, as i've now migrated all my data using this format, as the +<build> didn't work.

Yes - they are "self-connectors". We've now bought an externally signed certificate, as it seemed like the simpler option (the in house cert option was causing other issues too). However that hasn't resolved the issue with the self-connectors.

However, I've just edited those connectors manually to use http rather than https, and that has resolved the issue. But It's not really an ideal solution.

So it looks like from inside the docker container it's still not "trusting" the externally signed certificate.

@stevedennis - Thanks - switching to a trial of Basic Edition resolves the issue. However i'm fairly sure you don't get a UI warning when you setup a feed-level permission on the Free Edition.

Also you can add personal API keys in the free edition without warning - in fact on the API keys page, you even get a tick saying 'personal APU keys are enabled'

It's not the feed that connects directly to npmjs.org that has these errors, it's the feed that aggregates the other two - so it's almost as if it's having a problem with it's own feeds?

ProGet is running under docker, and I don't think your docker container has curl - so that makes it tricky.

Proget 2024.36 (build 5) - Free edition

I've created 3 NPM feeds:
first one connects to npsjs.org in order to cache packages
seconds one has no connectors, and is for local packages
third one aggregates the other two

If you view the feed page for the aggregate feed - you see error messages for both the connectors:

The ProGet server has a valid SSL certificate - Although, if it's relevant, it is issued by our own internal Certificate Authority.

There are no message showing in the Diagnostic Centre.