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

[BUG] Failed to publish package to registry.npmjs.org #7770

Closed
2 tasks done
SukkaW opened this issue Sep 8, 2024 · 2 comments
Closed
2 tasks done

[BUG] Failed to publish package to registry.npmjs.org #7770

SukkaW opened this issue Sep 8, 2024 · 2 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps

Comments

@SukkaW
Copy link

SukkaW commented Sep 8, 2024

Is there an existing issue for this?

  • I have searched the existing issues

This issue exists in the latest npm version

  • I am using the latest npm

Current Behavior

npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm error code CA_CREATE_SIGNING_CERTIFICATE_ERROR
npm error error creating signing certificate - (502) Bad Gateway
npm error cause (502) Bad Gateway

Expected Behavior

npm should be published normally.

Steps To Reproduce

https://github.com/SukkaW/foxact/actions/runs/10762545052/job/29843165244

Environment

  • npm: 10.8.2
  • Node.js: 20.17.0
  • OS Name: Ubuntu
  • System Model Name: GitHub Actions Ubuntu Latest
  • npm config:
@SukkaW SukkaW added Bug thing that needs fixing Needs Triage needs review for next steps labels Sep 8, 2024
@milaninfy
Copy link
Contributor

@SukkaW Is this still happening ? If yes and if you have a reproduction steps that can consistently reproduce this error locally then please provide.

@SukkaW
Copy link
Author

SukkaW commented Sep 13, 2024

@SukkaW Is this still happening ? If yes and if you have a reproduction steps that can consistently reproduce this error locally then please provide.

I guess the issue is related to the registry server, not the cli. Closing.

@SukkaW SukkaW closed this as completed Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps
Projects
None yet
Development

No branches or pull requests

2 participants