Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-14920

When publishing npm packages with --tag <tag> it affects the "latest" tag

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 5.4.6
    • Fix Version/s: 5.9.0
    • Component/s: NPM
    • Labels:
      None
    • Regression:
      Yes

      Description

      When publishing npm packages with --tag <tag> it affects the "latest" tag
      When the --tag option is used while publishing a package, it should not set the latest tag to the published version

      Steps to reproduce:
      1. create a new package.json with version 1.2.0
      2.run $ npm publish
      3. edit the same package.json, change the version to 1.3.0
      4. run $ npm publish --tag next
      5. run $npm install <pck-name>@latest

      You can see that ,after publishing both versions (“1.3.0” was tagged as next, not latest), when attempting to install the latest, “1.3.0” is installed.
      Which should not happen, as the latest is 1.2.0 because we tagged 1.3.0 as next, not latest

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                galba Gal Ben Ami
                Reporter:
                mohammadt Mohammad Tibi
                Assigned QA:
                Nadav Yogev
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: