Hi,

There appears to be some disparity between the npm min-release-age and the ProGet Recently published rule on the feed.

Setup

ProGet 2025.25 (Build 11)

.npmrc:

registry=https://my-proget-server/npm/npm-public/
min-release-age=7

ProGet Use Connector Publish Date enabled.

ProGet npm feed has Recently published (7 days).

Install

Run npm install for the latest applicable version of @hono/node-server

> npm i @hono/node-server@latest
npm error code E400
npm error 400 Bad Request - GET https://my-proget-server/npm/npm-public/%40hono/node-server/-/node-server-1.19.14.tgz - Package is Recently Published

In Proget @hono/node-server-1.19.14 has a publish date of the 2026-04-13 02:20:00:

I ran the npm install on 2026-04-20 15:12 BST, minus 7 days is 2026-04-13 15:12 BST. That's greater than the ProGet npm package date of 2026-04-13 02:20:00.

If I change my npm config to have min-release-age=8, then the install works fine. Is this some issue with timezones?

Thanks!

Hi

We updated to 2025.9 and NuGet packages are now being displayed with incorrect casing in the Visual Studio Package Manager.

ProGet 2025.9:

Nuget.Org:

It only appears to be an issue on packages we had not downloaded before the update to 2025.9.
This may or may not be related to this post: https://forums.inedo.com/topic/5477/packages-with-noncanonical-names-errors-on-internalized-packages?_=1757496394015

Hi,

We upgraded to 2025.9 after testing in our dev environment and ProGet is now importing PyPi packages from the drop folder

Thanks!

Hi @atripp,

I really appreciate you looking into this and sorting a fix so quickly. I'll hold off until the patch this Friday - we can temporarily work around the issue by manually uploading individual packages.

Thanks,
Ashley

Hi,

We upgraded our Windows ProGet instance to 2025.7 and are now seeing issues with the ProGet feed drop paths not importing files. It detects files dropped into the folder but the warning path it outputs is a weird combination of the feed storage and the import path.

Our configuration:
Feed name: pypi-internal
Feed type: PyPi
Storage Path: E:\.pypi\F5
Drop Path: C:\ProGetDrop\pypi-internal
ProGet version: 2025.7 (Build 12)
Windows Version: Windows Server 2019

Local Service Output

DEBUG: Found C:\ProGetDrop\pypi-internal\mypythonpackage-0.9.0-py3-none-any.whl
WARN: Error installing package: The filename, directory name, or volume label syntax is incorrect. : 'E:\.pypi\F5\mypythonpackage\0.9.0\C:\ProGetDrop\pypi-internal'
DEBUG: Deleting files...
DEBUG: Indexed 0 packages in pypi-internal feed.

Note that the Warning path is incorrect for a the file that is in: C:\ProgGetDrop\pypi-internal\mypythonpackage-0.9.0-py3-none-any.whl

The service has access to the directory and this was working fine before the upgrade. Any help is much appreciated.