'Cannot publish over existing version', regardless of version #4298
Comments
this is causing pillarjs/multiparty#39 |
Experiencing a similar problem for the past several days. No matter what version in package.json I set, I can't publish. Trying to unpublish and then trying again results in EPUBLISHCONFLICT. Here's the log for the first publish attempt:
|
I had the same problem with express-negotiator and npm 1.3.3. The latest version is 0.4.1, and I could not publish 0.4.2:
Updating to npm 1.4.6 fixed it! |
npm < 1.4 did not publish atomically, which meant that sometimes race conditions and other synchronization issues could crop up between the client and the server. Since we've fixed that (and removed the ability to republish the same version of a package), these issues have been addressed, and should only be encountered when running obsolete versions of npm. Closing this issue as resolved! |
When I run
npm publish
in my project, I get the error:Updating the version has no effect.
My package is named 'just-the-job'.
When I run 'npm view just-the-job' there is no output.
When I run 'npm unpublish just-the-job --force' I get the error:
UPDATE: The problem was fixed overnight - all other versions disappeared and I was able to publish version 0.0.0.
The text was updated successfully, but these errors were encountered: