Closed wesleytodd closed 3 years ago
You're right. That's likely what happened. I'll publish the missing tags, but end of the day, I should automate publishing of new tags.
Thanks for the quick response and 👍 on automation. There are some good GH actions for this you can probably use. Want me to close this now, or will you once the versions are published?
I can close when the versions are published.
All published.
Hey @spiermar, I noticed that a few versions are not published to the public npm registry despite being tagged. Our monitoring caught your recent publish and I am guessing they were just accidentally published on the Netflix internal registry.
curl https://registry.npmjs.com/d3-flame-graph | jq ".versions | keys[]"
It looks like the
4.0.0 - 4.0.5
range is what's missing. It should be a matter of just runningnpm publish
after checking out each tag. Hope that helps!