Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automated npm publish broken #209

Closed
tjduigna opened this issue Nov 1, 2020 · 1 comment
Closed

Automated npm publish broken #209

tjduigna opened this issue Nov 1, 2020 · 1 comment

Comments

@tjduigna
Copy link
Contributor

tjduigna commented Nov 1, 2020

Describe the bug
Last commit to master including version bumping the JS package failed to auto-publish.

To Reproduce
See the travis log here https://travis-ci.org/github/exa-analytics/exatomic/jobs/740498208#L3810
and the relevant log snippet:

npm notice === Tarball Details === 
npm notice name:          exatomic                                
npm notice version:       0.5.3                                   
npm notice package size:  750.5 kB                                
npm notice unpacked size: 3.3 MB                                  
npm notice shasum:        1d603d3c483d894fa9bde10453604e81f95f2afe
npm notice integrity:     sha512-1ugoEuzgCbvws[...]K6/1ozeKHlyhQ==
npm notice total files:   35                                      
npm notice 
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/exatomic - Not found
npm ERR! 404 
npm ERR! 404  '[email protected]' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Expected behavior
Version-bumped pushes to master should successfully publish the npm package.

Desktop (please complete the following information):

  • OS: Travis build server
  • Version: all new JS versions

Additional context
The travis configuration should be tied to the organization's npm account.

@tjduigna
Copy link
Contributor Author

tjduigna commented Nov 3, 2021

Closing in favor of #231 where a permanent fix will be considered

@tjduigna tjduigna closed this as completed Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant