Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 5.2.1, 5.4.6
    • Fix Version/s: 6.1.0
    • Component/s: NPM
    • Labels:
      None

      Description

      Currently Artifactory calculates the value of 'latest' tag either based on SemVer or when the package was published. Both of these are incorrect.

      As an npm user I want to be able to tag 3.0.0 as latest and 4.0.0-pre as next.

      given version 3.0.0, npm publish should implicitly set 'latest' to 3.0.0
      given version 4.0.0-pre, npm publish --tag next should set 'next' to 4.0.0-pre without affecting 'latest' (3.0.0)

      This issue dates back to https://www.jfrog.com/jira/browse/RTFACT-8184?focusedCommentId=40055&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-40055.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rotemk Rotem Kfir
                Reporter:
                vanjan Jan Klosinski
              • Votes:
                4 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: