lerna: [Bug] README.md is not published to npm

Awesome! Thanks @bcoe! The emoji don’t exist to express my excitement!

Thanks! Giving credit where credit is due, the whole backend team at npm has been working on infrastructure this makes solving problems like this much easier (we’ve been rolling out a database that was @chrisdickinson’s mad-science idea). I’m really excited to make the tag workflow elegant, for the community and for the benefit of my own OSS projects.

Alright!!! An update to this issue: it should be fixed (via npm side)!

So I just published 6.22.0 yesterday and was thinking about publishing to the latest tag first instead of first lerna-temp then moving to latest but forgot. Then I was checking the readme’s and it looked like they were already updated magically!?

Turns out @bcoe had been working on fixing this issue, so it looks like it’s all good for us on this one?

it now renders the README directly from the package, rather than pulling it out at publish time.

---

We haven’t published a new babel version in a month (>30 days)

Example with babel-core:

https://www.npmjs.com/package/babel-core

https://github.com/babel/babel/pull/5101/files (5 days ago)

EDIT:

😍😍😍😍😍😍 😍😍😍😍😍😍

@tomwayson Hey 👋

So, rather than always pointing to the last published README file, we now point to whatever README is pointed to by the latest tag of npm. so, if you have a workflow in which you publish to a beta tag (as an example) and then use npm dist-tag add to switch this tag, you will see the appropriate README after the swap has taken place.

Awesome! Finally! 🎉