-
OneDev currently does not display npm
dist-tagsin the package UI. The tags are stored on their target package versions and exposed through the npm registry API, which is whynpm dist-tag ls <package>and installs by tag work correctly.At present, OneDev stores only the current tag-to-version association; it does not persist a separate last-updated timestamp for each tag. Therefore the requested UI, especially the “last updated” value, would require a product enhancement and additional tag-history metadata rather than enabling an existing view.
For now, please use
npm dist-tag ls <package>(ornpm view <package> dist-tags) to inspect the current mappings. -
Name Previous Value Current Value Type
Question
Improvement
-
-
Name Previous Value Current Value Priority
Normal
Critical
-
-
As the assignee, I am relevant to taking this enhancement forward, but I cannot prepare the implementation because the
servicedeskaccount does not have write-code permission inonedev/server(the issue checkout failed with HTTP 403). Please grant the required permission or reassign the implementation to someone with repository write access. -
-
| Type |
Improvement
|
| Priority |
Critical
|
| Assignee | |
| Labels |
No labels
|
Problem
When publishing npm packages to the OneDev npm registry,
dist-tagsare correctly stored and resolvable vianpm dist-tag ls, but they are not visible anywhere in the OneDev package UI.The package page shows versions and their metadata, but there is no section showing which dist-tags (e.g.
latest,dev-develop,dev-feature-branch) point to which versions.Evidence
A build published
@abc/[email protected]with tagdev-issue-1519-shared-codec-use-npm-dist-tags. The build log fromnpm dist-tag lsconfirms three tags exist on the registry:The
npm install @abc/shared-codec@dev-issue-1519-shared-codec-use-npm-dist-tagscommand also resolves correctly (11 packages installed).However, when viewing the package in the OneDev UI, none of these dist-tags are shown. Users have no way to see which tags exist or which version each tag points to without CLI access.
Request
Add a dist-tags section to the package detail page in the OneDev UI that shows:
This would make the npm package management experience in OneDev comparable to other registries (e.g. npmjs.com shows dist-tags on the package versions tab).