Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.7.2
    • Component/s: NPM
    • Labels:
      None

      Description

      Given I have a package named `jon` at version `0.1.0-a`
      And I call `npm publish --tag=next`
      Then I expect `npm dist-tag ls jon` to show `next: 0.1.0-a`

      instead it publishes without error.

      To work around, I call `npm dist-tag add jon@0.1.0-a next`

      My word around doesn't include setting the `latest` tag back to the appropriate version (`latest` should not update when using `--tag` with `npm publish`)

      Note, the workaround wasn't available until 4.1 thanks to https://www.jfrog.com/jira/browse/RTFACT-7400

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                shayb Shay Bagants
                Reporter:
                jonathan.hoguet@dealer.com Jon Hoguet
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: