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

Rename NPM package to kubo #51

Closed
4 tasks done
lidel opened this issue Jul 19, 2022 · 3 comments · Fixed by #63
Closed
4 tasks done

Rename NPM package to kubo #51

lidel opened this issue Jul 19, 2022 · 3 comments · Fixed by #63
Assignees
Labels

Comments

@lidel
Copy link
Member

lidel commented Jul 19, 2022

Part of ipfs/kubo#8959

TODO

  • see if we can get kubo on NPM – tracked in Transferring kubo NPM package name queerviolet/werkit#1 (if it does not work out, we could go with kubo-bin)
  • decide if we want to do dual-publishing to both names, or deprecate old one
  • update CI to publish to new name
  • deprecate go-ipfs and point at kubo
@lidel lidel added the need/triage Needs initial labeling and prioritization label Jul 19, 2022
@lidel lidel moved this to 🥞 Todo in IPFS Shipyard Team Jul 19, 2022
@lidel lidel self-assigned this Jul 19, 2022
@lidel lidel added status/in-progress In progress and removed need/triage Needs initial labeling and prioritization labels Jul 19, 2022
@lidel lidel moved this from 🥞 Todo to 🛑 Blocked in IPFS Shipyard Team Aug 4, 2022
@SgtPooki
Copy link
Member

SgtPooki commented May 4, 2023

FYI, the ipfs namespace on npmjs is owned by Juan and we just need to figure out what he needs to do to transfer ownership to one of our service accounts, and then we could get @ipfs/kubo if that's something we want to do.

@galargh
Copy link
Contributor

galargh commented May 15, 2023

https://www.npmjs.com/~npm-service-account-ipfs is the most suitable account for this I think.

@lidel lidel pinned this issue Aug 18, 2023
@lidel
Copy link
Member Author

lidel commented Aug 18, 2023

We now have https://www.npmjs.com/package/kubo and I've invited npm-service-account-ipfs to be one of the maintainers.

I don' think dual-publishing is worth it, as it would require additional code that modifies package.json in between builds.
Let's switch to a new name, and once Kubo 0.23 ships, deprecate the go-ipfs with message asking people to switch to kubo.

PR that renames things: #63

lidel added a commit that referenced this issue Aug 18, 2023
lidel added a commit that referenced this issue Aug 18, 2023
lidel added a commit that referenced this issue Aug 18, 2023
galargh pushed a commit that referenced this issue Aug 18, 2023
@github-project-automation github-project-automation bot moved this from 🛑 Blocked to 🎉 Done in IPFS Shipyard Team Aug 18, 2023
lidel added a commit to ipfs/ipfs-desktop that referenced this issue Aug 18, 2023
lidel added a commit to ipfs/ipfs-webui that referenced this issue Aug 18, 2023
SgtPooki pushed a commit to ipfs/ipfs-desktop that referenced this issue Aug 22, 2023
SgtPooki added a commit to ipfs/ipfs-webui that referenced this issue Aug 22, 2023
cc ipfs/npm-kubo#51
cc ipfs/kubo#8959

Co-authored-by: Russell Dempsey <1173416+SgtPooki@users.noreply.github.com>
@lidel lidel unpinned this issue Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants