[RTFACT-14920] When publishing npm packages with --tag <tag> it affects the "latest" tag Created: 11/Sep/17  Updated: 10/Jun/18  Resolved: 28/Jan/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: NPM
Affects Version/s: 5.4.6
Fix Version/s: 5.9.0

Type: Bug Priority: High
Reporter: Mohammad Tibi Assignee: Gal Ben Ami
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates RTFACT-14111 npm 'latest' tagging is broken Resolved
Relationship
relates to RTFACT-8184 `npm publish --tag={tag} not working Resolved
is related to RTFACT-16009 `latest` dist tag does not point back... Resolved
Regression:
Yes
Assigned QA: Nadav Yogev

 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


Generated at Sun Aug 25 01:20:42 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.