-
Type:
Bug
-
Status: Done
-
Resolution: Fixed
-
Affects Version/s: 5.9.0
-
Fix Version/s: 6.6.3
-
Component/s: None
-
Labels:None
-
Severity:Medium
-
Requirement Status:
Steps to reproduce:
1: install two versions of a package and move it to a local npm repo (I used grunt)
2: with npm set up, do: npm dist-tag add grunt@1.0.1 latest
+latest: grunt@1.0.1
3: see that the latest tag is still 1.0.2: npm dist-tag ls grunt
latest: 1.0.2
The latest tag is never updated, even though the metadata is updated apparently:
2018-03-03 00:00:29,194 [http-nio-8081-exec-17] [INFO ] (o.j.r.n.r.h.AbstractNpmRepoHandler:164) - Updating npm package metadata '.npm/grunt/package.json' into repo 'npm-local'
Tagging seems to work for tags that aren't latest though:
npm dist-tag add grunt@1.0.1 testtag
npm dist-tag ls grunt
latest: 1.0.2
testtag: 1.0.1
- is duplicated by
-
RTFACT-17286 npm tagging while publishing also updates latest tag
- Done
- is related to
-
RTFACT-17732 NPM latest tag is not listed accordingly by Artifactory
- Open
- relates to
-
RTFACT-14920 When publishing npm packages with --tag <tag> it affects the "latest" tag
- Done
- triggered
-
RTFACT-20127 NPM tagLatestByPublish System Property does nothing
- Done