<![CDATA[[ProGet] Incorrect package publish date affecting policies]]>Hi,

In our setup, we have an 'external' feed and a 'curated' feed for each package ecosystem. Each 'external' feed has relevant connectors to the registries. When we would like to open up use of packages internally, the packages are promoted (from the 'external' feed) to our 'curated' feed.

We have noticed that, for our 'curated' feeds, the package publish date is the date the package has effectively been promoted (not the original package publish date). On our 'curated' feeds, we currently have the 'Aged package (3 years)' and 'Recently published (14 days)' policies enabled and set to 'warn'. Currently warnings are not showing up for aged packages and incorrectly showing on the other hand even though they are not recently published. This also causes issues with the Yarn 'npmMinimalAgeGate' check.

We have ensured, the below, 'Feeds.UseConnectorPublishDate' setting is enabled.

Just wondering if this behaviour is occurring due to our feed setup, external -> curated, and therefore the above setting doesn't work because the packages are just promoted to our 'curated' feeds?

Thanks!

]]>https://forums.inedo.com/topic/5801/proget-incorrect-package-publish-date-affecting-policiesRSS for NodeFri, 24 Jul 2026 20:33:31 GMTThu, 23 Jul 2026 14:35:18 GMT60<![CDATA[Reply to [ProGet] Incorrect package publish date affecting policies on Fri, 24 Jul 2026 18:57:41 GMT]]>Hi @amy.j ,

This behavior is expected, as the publish date is not carried over via a promotion.

In retrospect, it should have - but this is the sort of behavior we need to be careful about changing in a maintenance release. We'll discuss this internally and decide - please stay tuned, wehope to update by end of next week.

Thanks,
Steve

]]>https://forums.inedo.com/post/19886https://forums.inedo.com/post/19886Fri, 24 Jul 2026 18:57:41 GMT