The npm latest version of express is 5.0.0-beta.2 !!!

[drobnikj]

Can you double-check that it is on purpose?

I cannot see any notes about this major release in the change log.
This can potentially break a lot of stuff without proper release notes and migration guide.

Did I miss anything?

[UlisesGascon]

I am working on it, thanks for the ping @drobnikj

[UlisesGascon]

I close the issue as this is now fixed. Thanks for the CLI tricks @jonchurch

[wesleytodd]

Was not on purpose. Just an oversight in a manual process being done for the first time in my part.

[fire015]

This is still visible on NPM fyi @wesleytodd @UlisesGascon

[wesleytodd]

Not for me.

[fire015]

@wesleytodd Sorry what I meant was, is beta.2 supposed to be showing up at all in NPM considering there is no tag/release or changelog about it in this repo?

[wesleytodd]

is beta.2 supposed to be showing up at all in NPM considering there is no tag/release or changelog about it in this repo?

Yes it was intentional to publish, just not without --tag=next. I added the releases on GH now (including the new one just published). Sorry for the confusion.

[fire015]

Thanks, it just looked suspicious (you hear about NPM packages been hacked all the time) 👍

[wesleytodd]

Yep! Thanks for checking!

[jonchurch]

Yep thanks for noticing and reporting @fire015

The impact this would have had during the couple of hours that latest pointed to v5 was that folks who npm i express would have gotten v5 beta instead of v4.

It also likely triggered some "hey there's a new major available" notices to folks.

because NPM lets you change where latest points without a republish, we just fixed it once we noticed by doing a
npm dist-tag add express@<version> latest to point to the correct v4 release