Better maintained versions in NPM registry

[clemens]

Is your feature request related to a problem? Please describe.

The version history on npmjs.com and the registry as a whole can be incredibly useful tools. However, that is only true if it's reasonably managed.

The fact that every PR seems to be released as a version to the registry clutters it and limits its usefulness. Moreover, it's debatable whether or not the currently tagged versions there make sense:

• Is 6.0.28-alpha.3 really the current "debug" release?
• Is 6.5.17-alpha.0 really the current "prerelease"?
• Does it make sense that 7.1.0-alpha.29 is tagged "future"?
• Does a "canary" tag even make sense when it seems to always just point to whatever happens to be the latest PR build?
• Why are 2 (seemingly random) 7.1.1 PRs included explicitly in the tag list?

Describe the solution you'd like

• Only official releases (which can, of course, include alpha and beta releases as well as release candidates) should be pushed
• Tags should be reviewed and cleaned up and an official documentation should be added which tags are considered official and what they mean

Describe alternatives you've considered

No response

Are you able to assist to bring the feature to reality?

no

Additional context

No response