Skip to content

chore: change organization from metamask to bitcoindevkit #1

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

notmandatory
Copy link
Member

@notmandatory notmandatory commented Aug 15, 2025

Description

Updated organization meta data that references metamask to bitcoindevkit.

Notes to the reviewers

I had to reduce the number of keywords in Cargo.toml to five to match what crates.io allows for the keywords field.

I also created this PR to trigger the CI so we can add those jobs to our default branch protection checks.

Changelog notice

  • Updated organization meta data that references metamask to bitcoindevkit.

Checklists

All Submissions:

  • I've signed all my commits
  • I followed the contribution guidelines
  • I ran cargo fmt and cargo clippy before committing

@notmandatory notmandatory self-assigned this Aug 15, 2025
@notmandatory
Copy link
Member Author

notmandatory commented Aug 15, 2025

@darioAnongba I didn't test publishing yet, I want to figure out first if we want to keep the NPM name "bitcoindevkit" or change it to "bdk_wasm". If we change it to `bdk_wasm" should we change the repo name also?

Since the organization name is now "bitcoindevkit" it seems weird to me have a package called "@bitcoindevkit/bitcoindevkit" rather than "@bitcoindevkit/bdk_wasm".

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 this pull request may close these issues.

1 participant