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

release: 17.0.0 #133

Merged
merged 11 commits into from
Jan 6, 2025
Merged

release: 17.0.0 #133

merged 11 commits into from
Jan 6, 2025

Conversation

gantunesr
Copy link
Member

Description

This is the release candidate for version 17.0.0. See the CHANGELOGs for more details.

@gantunesr gantunesr requested a review from a team as a code owner December 18, 2024 17:39
@gantunesr gantunesr changed the title Release/17.0.0 release: 17.0.0 Dec 18, 2024
darioAnongba
darioAnongba previously approved these changes Dec 19, 2024
@ccharly ccharly added this pull request to the merge queue Jan 6, 2025
Merged via the queue into main with commit 928850f Jan 6, 2025
29 checks passed
@ccharly ccharly deleted the release/17.0.0 branch January 6, 2025 12:19
ccharly added a commit to MetaMask/core that referenced this pull request Jan 13, 2025
…eature (#5136)

## Explanation

Some accounts packages were not properly versioned when introducing the
new `scopes` feature. This has now been fixed and this PR bumps each
accounts packages accordingly.

## References

- #5066
- MetaMask/accounts#137
- MetaMask/accounts#133

## Changelog

### `@metamask/accounts-controller`

- **CHANGED**: **BREAKING:** Bump `keyring-internal-api` to `^2.0.0`
- **CHANGED**: **BREAKING:** Bump `eth-snap-keyring` to `^8.0.0`

### `@metamask/chain-controller`

- **CHANGED**: **BREAKING:** Bump `keyring-internal-api` to `^2.0.0`

### `@metamask/keyring-controller`

- **CHANGED**: **BREAKING:** Bump `keyring-internal-api` to `^2.0.0`

## 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
- [ ] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes
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.

3 participants