Currently, when we release a preview version (beta, alpha, or RC), it publishes it with next tag on the NPM registry:
https://github.com/getsentry/craft/blob/master/src/targets/npm.ts#L181-L189
However, when after a few iterations we perform a complete release, with a non-preview version, this tag is never cleaned up, and it points to the older version than latest, which is not valid by definition, as next should always point to at least latest (or newer).
It would be nice if we could detect that the next was pointing at the preview version of the "about to be released" version, and if that is the case, call npm dist-tag rm @sentry/node next to clean it up.
An example from @sentry/node repository:
Currently, when we release a preview version (beta, alpha, or RC), it publishes it with
nexttag on the NPM registry:https://github.com/getsentry/craft/blob/master/src/targets/npm.ts#L181-L189
However, when after a few iterations we perform a complete release, with a non-preview version, this tag is never cleaned up, and it points to the older version than
latest, which is not valid by definition, asnextshould always point to at leastlatest(or newer).It would be nice if we could detect that the
nextwas pointing at the preview version of the "about to be released" version, and if that is the case, callnpm dist-tag rm @sentry/node nextto clean it up.An example from
@sentry/noderepository: