@dean-houston said in Published timestamp resets after pulling remote npm packages:

"Admin > Advanced Settings > Use Connector Publish Date"

Thanks a lot for your fast reply, changing that setting works like a charm.

I'm using ProGet with caching from the npm registry. When a package is not yet pulled to the ProGet instance, the Published timestamp correlates with the publish date in the npm registry, which is correct:

However, after pulling the package, the Published timestamp is reset to the date of the pull operation:

I would have expected the Published date to correlate with the publish date in the upstream npm registry. This is a problem for me, because I am using pnpm with the minimumReleaseAge option which requires the Published timestamp to be accurate.