Use pre-release tags when publishing to NPM about skin HOT 11 CLOSED

And ... I was able to give myself access to publish. I was also able to update the latest tag to v3.3.2, which, at the time of this writing, is the actual latest version.

from skin.

Urgh, that sucks that the npm prerelease command (npm version preminor) does not satisfy the semver prerelease convention (or maybe, and possibly more likely, I just misunderstood the command). Should I unpublish this version from NPM? I believe I have 24 hours to do so.

EDIT: oh wait, I've just seen your nom dist-tag add comment. So no need to unpublish, right?

from skin.

Sean, what's your NPM username? Will add you to @eBay npm org.

from skin.

I believe it’s seangates.

from skin.

And yes, no need to unpublish. Just add the dist-tag.

Going forward we would just add the --tags beta to our publish command.

from skin.

Ok. I ran npm dist-tag add @ebay/[email protected] beta

from skin.

👍 I will try again tomorrow.

from skin.

So ... per our Slack conversation about adding the beta tag to the other releases? Well, having run the yarn info @ebay/skin I see that the beta tag is now set on 3.0.0-0 ... only.

Oops.

It appears that the tag can only be used on one package version at a time. So, I think we need to run the npm dist-tag add @ebay/[email protected] beta to set it to the latest beta. I will try and do this.

from skin.

I guess I don't have NPM access to the @ebay scope yet. 😉

from skin.

Can we close this now? Or do we need to add anything else to the docs?

from skin.

We're good. Closing.

from skin.