Publish older versions without a tag

[watson]

No description provided.

[ljharb]

This would be great; i currently use https://npmjs.com/safe-publish-latest to prevent accidentally publishing a backport as “latest”.

Even better (on top of this) would be if the tag could be overwritten in prepublish - then i could have a package that removed the “latest” tag when it was unsafe.

[zkat]

The team had a meeting and we're happy to say we've ratified this! Thanks for the RFC, and I look forward to having this. Since it's a breaking change, we won't be able to have it until npm@7, but it should be straightforward to implement and wait for the final thing 👍

[evocateur]

In the meantime, a better way to mitigate this in long-lived maintenance branches is to immediately set publishConfig.tag in the package.json to an appropriate value. All future publishes from that branch will use that (non-"latest") value as the dist-tag, no flags necessary.

[ljharb]

@evocateur that’s a great workaround, but it still ends up creating a tag that i have to remove after publishing.

[evocateur]

@ljharb Oh, fair enough. At least it wouldn't be "latest" by default in the scenario I described. Still doesn't avoid a tag altogether, you are correct.

[ljharb]

@zkat couldn’t something like --no-tag be added as a semver-minor, and the breaking change later be making that the default?

[evocateur]

I wouldn't recommend treating a string option as a (negatable) Boolean. It's more trouble than it's worth, in my experience.

…

On Dec 21, 2018, at 08:43, Jordan Harband ***@***.***> wrote: @zkat couldn’t something like --no-tag be added as a semver-minor, and the breaking change later be making that the default? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[ljharb]

Oh sure, maybe --without-tag then - bikeshed aside it seems totally doable as a semver-minor