Remove -alpha.0 from versions?

[korywka]

It looks like this package is still in alpha but it is not.

[MasterKale]

6.3.0 is definitely in alpha, it's a preview build containing a WIP implementation of Device Public Key support. It's not intended for use in production environments; everyone else should still be on 6.2.0.

Is an npm install or npm upgrade pushing 6.3.0-alpha.0 on you?

[korywka]

Oh thanks. I thought it was added by lerna by mistake.

Sorry to be a distraction.

[lkwr]

It seems this is still a problem. When looking at the @simplewebauthn/typescript-type package at npm, it shows the version 6.3.0-alpha.1 but I should expect to see the latest stable release (in this case 6.2.1):

This can be a bit confusing as you may think the whole package is "alpha". I would recommend that pre-released versions (such as alpha, betas and so) should NOT be tagged as latest in the npm registry. This solves the problem of showing pre-released versions on the default package page.

[MasterKale]

Huh, interesting, browser and server both show 6.2.2:

I suppose what happened here is that 6.2.2 didn't include any changes to typescript-types and so it's still showing the alpha release.

Thank you for pointing out that latest is what determines the version that shows up there. I use lerna publish to get things up on NPM, perhaps there's a flag there I need to use when pushing up alpha launches. I'll take a look next time I need to do so.

[lkwr]

Maybe something like this (--dist-tag) or that (--canary) should do the trick with lerna publish.