npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

Publish failing due to 500 registry error

What I Wanted to Do

Jenkins ran npm publish.

We auto publish packages to

What Happened Instead

The npm publish command ran into an error.

[ature_dont_run_reset_script-VDECCXCNHRXCLCGXYGLBXSLK5B57XB5WU74IOJXSSJN4KVNAYFKA] Running shell script
  • npm publish --tag feature~dont_run_reset_script --ignore-scripts
    npm ERR! publish Failed PUT 403
    npm ERR! code E403
    npm ERR! You cannot publish over the previously published versions: 4.0.1-2268a3ea-b2. : bpmn-studio
    npm ERR! A complete log of this run can be found in:

npm ERR! /var/lib/jenkins/.npm/_logs/2018-08-07T08_18_07_699Z-debug.log

script returned exit code 1

But the version was sucessfully published!

You can see the full build here

Reproduction Steps

Sadly this erros happens only sometimes. We can not give any details on how to reproduce execpt running npm publish. This errors seems to be a problem with the npm registry backend.


Because of the strange 5 links limit I postet the debug log here:

Platform Info

+ npm --versions

{ npm: '5.6.0',
  ares: '1.10.1-DEV',
  cldr: '32.0',
  http_parser: '2.8.0',
  icu: '60.1',
  modules: '57',
  napi: '3',
  nghttp2: '1.32.0',
  node: '8.11.3',
  openssl: '1.0.2o',
  tz: '2017c',
  unicode: '10.0',
  uv: '1.19.1',
  v8: '6.2.414.54',
  zlib: '1.2.11' }

+ node -p process.platform

The team I work on keeps periodically running into 500’s on publish as well. Sometimes it complains it is already published other times it just flat out fails. I’m not sure if it makes a difference but our use case is publishing to private repositories under an npm organization.

This is a duplicate of "Npm publish" hangs and never finishes