Webpack-cli: Beta version accidentally tagged as latest in NPM?

[teuneboon]

Let me preface this with the fact that I'm not too familiar with how versioning works with npm, so I might be wrong here.

When I look at https://www.npmjs.com/package/webpack-cli it looks like 4.0.0-beta.2 got the "latest" tag, but if I look at other projects like https://www.npmjs.com/package/vue and https://www.npmjs.com/package/eslint the alpha version isn't getting the "latest" tag there at least.

I came across this when webpack-cli accidentally got updated to 4.0.0-beta.2 a few hours ago on our CI server(which we should have version pinned a bit better).

[rishabh3112]

cc @ematipico

[silverwind]

Tag latest is generally supposed to be for stable releases, not beta version. I think this is an publishing error.

[geocolumbus]

There seems to be more than a handful of bugs. Did the wrong version get released?

[ematipico]

Yeah that was a mistake of mine! I will fix it ASAP! Sorry about that

[ematipico]

Hi,

Again, apologies for the inconvenience! It was my first release and of course I had to do something wrong 😅

Anyway, I released a patch release v3.3.11 which is stable and it contains only a bump of the version.
Also, I did release a beta version of npm under v4.0.0-beta.3.

[teuneboon]

Thanks for the fix, it seems to be correct to me now so I'll close this issue.