-
-
Notifications
You must be signed in to change notification settings - Fork 198
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 208.0.0 #4731
Release 208.0.0 #4731
Conversation
0d6bbe0
to
e23d9fe
Compare
7a31fca
to
5868653
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The following appear to be dev dependency updates, which we generally don't note in changelogs.
Edit: Although if they provide useful context for the team, keeping them shouldn't be an issue.
- Bump accounts related packages ([#4713](https://github.com/MetaMask/core/pull/4713)), ([#4728](https://github.com/MetaMask/core/pull/4728)) | ||
- Those packages are now built slightly differently and are part of the [accounts monorepo](https://github.com/MetaMask/accounts). | ||
- Bump `@metamask/keyring-api` from `^8.1.0` to `^8.1.4` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Bump accounts related packages ([#4713](https://github.com/MetaMask/core/pull/4713)), ([#4728](https://github.com/MetaMask/core/pull/4728)) | |
- Those packages are now built slightly differently and are part of the [accounts monorepo](https://github.com/MetaMask/accounts). | |
- Bump `@metamask/keyring-api` from `^8.1.0` to `^8.1.4` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes true, but I wanted to mark those since the introduction of our new monorepo on the account side. We have done some basic testing on the extension side (using our e2e and some manual testing with preview builds) but in case there's any regression (there should not) I thought it would be great to have this being commented somewhere in the CHANGELOG.
If you think that's "too much", I'm also ok removing those!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds perfectly reasonable to keep them. Just wanted to be sure their inclusion was intentional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
## Explanation This reverts commit 9949c81. The `assets-controllers` version was wrong for the last RC. So we have to revert this RC and re-create it while fixing the `assets-controllers` bad version. Version during that release [was `38.0.2`](https://github.com/MetaMask/core/blob/eb656db1704c6dcfa9474086434b267b15e62c97/packages/assets-controllers/package.json#L3) but it should have been `38.1.0`. ## References - #4731 ## Changelog N/A ## 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
## Explanation This is a RC for v208.0.0. See changelog for more details ## References N/A ## Changelog N/A ## 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
## Explanation This is a RC for v208.0.0. See changelog for more details ## References Initial attempt: - #4731 Revert of the failing 208.0.0: - #4733 ## Changelog N/A ## 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
Explanation
This is a RC for v208.0.0. See changelog for more details
References
N/A
Changelog
N/A
Checklist