Navigation

    Inedo Community Forums

    Forums

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. d.kimmich_0782
    3. Posts
    D
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Posts made by d.kimmich_0782

    • RE: Published timestamp resets after pulling remote npm packages

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

      posted in Support
      D
      d.kimmich_0782
    • Published timestamp resets after pulling remote npm packages

      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:

      af2c773f-084b-4c86-a68d-23eee6e6593f-image.png

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

      03e7e70b-d256-4299-87a3-9e3dac4e2fc6-image.png

      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.

      posted in Support
      D
      d.kimmich_0782
    • 1 / 1