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

Change npm name to kubo-rpc-client #1

Closed
SgtPooki opened this issue Aug 23, 2022 · 6 comments
Closed

Change npm name to kubo-rpc-client #1

SgtPooki opened this issue Aug 23, 2022 · 6 comments

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Aug 23, 2022

Originally from ipfs/kubo#9125

Ideally, we should have one Kubo client at https://github.com/ipfs/js-kubo-rpc-client and kubo-rpc-client on NPM.

@SgtPooki
Copy link
Member Author

The commit was pushed with 5256ba0 but we're blocked on npm publish because npm-service-account-ipfs doesn't have permissions to publish to https://www.npmjs.com/package/kubo-rpc-client. Currently only @lidel and @achingbrain (via ipfs-npm-publisher-bot) seem to have permissions.

@achingbrain could you give me and npm-service-account-ipfs permission to https://www.npmjs.com/package/kubo-rpc-client when you get a chance?

@SgtPooki
Copy link
Member Author

@SgtPooki
Copy link
Member Author

@SgtPooki
Copy link
Member Author

SgtPooki commented Sep 2, 2022

pushed empty commit with git commit -m "chore: empty commit to trigger release" --allow-empty. See https://github.com/ipfs/js-kubo-rpc-client/actions/runs/2981942342

@SgtPooki
Copy link
Member Author

SgtPooki commented Sep 6, 2022

currently troubleshooting latest failure:

npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/kubo-rpc-client - You do not have permission to publish "kubo-rpc-client". Are you logged in as the correct user?

https://github.com/ipfs/js-kubo-rpc-client/runs/8215114763?check_suite_focus=true

@SgtPooki
Copy link
Member Author

SgtPooki commented Sep 6, 2022

Finally got https://www.npmjs.com/package/kubo-rpc-client published with the latest changes, but it required manually publishing to npm with --otp=<code>. This SHOULD NOT be required, but no matter what I did npm wanted me to set the OTP

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

No branches or pull requests

1 participant