Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-24234

deleting npm package metadata does not delete it completely

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: NPM
    • Labels:
    • Notability:
      3

      Description

      1. Create a npm proxy repo
      2. Download an npm package metadata through the proxy - make note it references a version, for example 1.0.0
      3. The remote site unpublishes version 1.0.0 of the package
      4. Go to Browse and select the npm package metadata file - delete it.
      The intent of an admin doing this is to bring the locally cached tgz packages in line with what the remote actually has available.
      5. Download an npm package metadata through the proxy again - make note it it still references version 1.0.0, even though the remote no longer references that version and that version is no longer cached inside the proxy repository.

      Expected

      If the package metadata is deleted from NXRM, and there are tarballs also cached in the repo that are no longer at the remote, then NXRMs new package metadata should no longer reference the a non-existing version.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title