Skip to content

fix: move @metamask/keyring-controller to dependency in @metamask/accounts-controller #4425

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

Merged

Conversation

montelaidev
Copy link
Contributor

@montelaidev montelaidev commented Jun 14, 2024

Explanation

This PR moves @metamask/keyring-controller to dependency from devDependency in @metamask/accounts-controller

References

Changelog

@metamask/accounts-controller

  • CHANGED: move @metamask/keyring-controller from devDependencies to dependencies

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've highlighted breaking changes using the "BREAKING" category above as appropriate

@montelaidev montelaidev requested a review from a team as a code owner June 14, 2024 00:49
@montelaidev montelaidev merged commit 1178ad5 into main Jun 18, 2024
116 checks passed
@montelaidev montelaidev deleted the fix/keyring-controller-as-dev-dep-in-accounts-controller branch June 18, 2024 08:47
@montelaidev montelaidev mentioned this pull request Jun 25, 2024
3 tasks
staging-devin-ai-integration bot pushed a commit to Devin-Applications/core-devin that referenced this pull request Jul 11, 2024
…accounts-controller` (MetaMask#4425)

## Explanation

This PR moves `@metamask/keyring-controller` to dependency from
devDependency in `@metamask/accounts-controller`

## References

## Changelog

### `@metamask/accounts-controller`

- **CHANGED**: move `@metamask/keyring-controller` from
`devDependencies` to `dependencies`


## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've highlighted breaking changes using the "BREAKING" category
above as appropriate
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.

2 participants