search

npm / registry-issue-archive

An archive of the old npm registry issue tracker
https://npm.community
249 stars 47 forks source link

Published new version yesterday, npmjs.com still showing previous version today #100

Open jefflembeck opened 7 years ago

jefflembeck commented 7 years ago

Copied directly from https://github.com/npm/www/issues/84

Yesterday I published v0.22.0 of watson-speech (or Travis CI did on my behalf). The publish was successful, and npm info watson-speech shows the latest dist-tag as 0.22.0.

However, https://www.npmjs.com/package/watson-speech is still showing that v0.21.0 from two weeks ago is the latest release.

Any idea what's going on?

soldair commented 7 years ago

sometimes there is an error processing a job and something might be skipped we are working on the replacement for this backend but the module has been updated.

panzerdp commented 7 years ago

Hi @soldair,

I have exactly the same problem. I published a few hours ago a new library version 1.1.0 , however the Readme page still shows the old 1.0.0. The library: https://www.npmjs.com/package/voca npm install however installs the correct 1.1.0 version. How can I make it showing the correct version?

Thanks!