Conversation
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/@metamask/profile-sync-controller@0.1.4, npm/@metamask/selected-network-controller@16.0.0 |
Prithpal-Sooriya
left a comment
There was a problem hiding this comment.
Satisfied with the notifications side (@metamask/notification-services-controller, @metamask/profile-sync-controller)
|
|
||
| ## [Unreleased] | ||
|
|
||
| ### Changed |
There was a problem hiding this comment.
Are we releasing this package? If not, should we add these changelog entries in another PR?
There was a problem hiding this comment.
To include the changes in #4556, I added releases for:
ens-controller(a3308b8)gas-fee-controller(ac917f0)selected-network-controller,queued-request-controller61670f3transaction-controller,user-operation-controller773baa3
Every package with a diff in this PR is now being released (excluding json-rpc-engine).
| - Upgrade TypeScript to v5.0 and set `moduleResolution` option to `Node16` ([#3645](https://github.com/MetaMask/core/pull/3645)) | ||
| - Bump `@metamask/base-controller` from `^6.0.0` to `^6.0.2` ([#4517](https://github.com/MetaMask/core/pull/4517), [#4544](https://github.com/MetaMask/core/pull/4544)) | ||
| - Bump `@metamask/snaps-controllers` from `^8.1.1` to `^9.3.1` ([#3645](https://github.com/MetaMask/core/pull/3645)) | ||
| - Bump peerDependency `@metamask/snaps-controllers` from `^8.1.1` to `^9.3.0` |
There was a problem hiding this comment.
If we are bumping a peer dependency then this is a breaking change as the client will also need to upgrade this dependency. Should we bump this package to 0.2.0?
There was a problem hiding this comment.
@Prithpal-Sooriya How would you feel about using a minor version bump to indicate that there are breaking changes in the release?
There was a problem hiding this comment.
Upgraded both {notifications-services,profile-sync}-controller to 0.2.0: f842953
@Prithpal-Sooriya Let me know if this goes against the team's intentions. I can simply revert that commit.
| - Bump `@metamask/snaps-sdk` from `^4.2.0` to `^6.1.1` ([#3645](https://github.com/MetaMask/core/pull/3645), [#4547](https://github.com/MetaMask/core/pull/4547)) | ||
| - Bump `@metamask/snaps-utils` from `^7.4.0` to `^7.8.1` ([#3645](https://github.com/MetaMask/core/pull/3645), [#4547](https://github.com/MetaMask/core/pull/4547)) | ||
| - Bump `@metamask/utils` from `^8.3.0` to `^9.1.0` ([#4516](https://github.com/MetaMask/core/pull/4516), [#4529](https://github.com/MetaMask/core/pull/4529)) | ||
| - Bump peerDependency `@metamask/snaps-controllers` from `^8.1.1` to `^9.3.0` ([#3645](https://github.com/MetaMask/core/pull/3645)) |
There was a problem hiding this comment.
If we're bumping a peer dependency by a major then this would be a breaking change as it forces the client to also upgrade this package. Should we bump the version to 18.0.0?
|
Hi there! @MajorLift |
83060c1
| - Bump `@metamask/snaps-controllers` from `^8.1.1` to `^9.3.1` ([#3645](https://github.com/MetaMask/core/pull/3645), [#4547](https://github.com/MetaMask/core/pull/4547)) | ||
| - Bump `@metamask/snaps-sdk` from `^4.2.0` to `^6.1.1` ([#3645](https://github.com/MetaMask/core/pull/3645), [#4547](https://github.com/MetaMask/core/pull/4547)) | ||
| - Bump `@metamask/snaps-utils` from `^7.4.0` to `^7.8.1` ([#3645](https://github.com/MetaMask/core/pull/3645), [#4547](https://github.com/MetaMask/core/pull/4547)) |
There was a problem hiding this comment.
@MetaMask/accounts-engineers Should any of these be peer dependencies (esp. snaps-controllers)?
There was a problem hiding this comment.
Typically the snaps controller is added as a peer dependency, for the same reason as the other controllers. I don't see the others as being used as peer deps though.
Perhaps we can move the controller to be a peer dependency later, since it's a pre-existing issue.
|
It's worth noting that once we have our codeowners file updated, a PR covering the same packages as this one will require 6 approvals (accounts, assets, confirmations, notifications, wallet-api-platform, wallet-framework) possibly multiple times throughout the review process. One way to make this a little less painful might be to first ask for approval from codeowners who own more packages in the PR (wallet-framework, confirmations), before pinging codeowners who own less packages. |
Gudahtt
left a comment
There was a problem hiding this comment.
Left a few corrections mostly minor
Co-authored-by: Mark Stacey <markjstacey@gmail.com>
| ### Added | ||
|
|
||
| - Add and export object `USER_STORAGE_SCHEMA`, function `getFeatureAndKeyFromPath`, and type `UserStoragePath` ([#4543](https://github.com/MetaMask/core/pull/4543)) | ||
| - Add `connectSnap` method to the `JwtBearerAuth` class for connecting to snap after initializing the Profile Sync SDK ([#4560](https://github.com/MetaMask/core/pull/4560)) |
There was a problem hiding this comment.
@Prithpal-Sooriya I added an entry for the new commit adding connectSnap.
This is the release candidate for `v180.0.0`: - `@metamask/accounts-controller@18.0.0` (major) - `@metamask/assets-controllers@37.0.0` (major) - `@metamask/chain-controllers@0.1.1` (patch) - `@metamask/ens-controller@13.0.1` (patch) - `@metamask/eth-json-rpc-provider@4.1.2` (patch) - `@metamask/gas-fee-controller@19.0.1` (patch) - `@metamask/keyring-controller@17.1.2` (patch) - `@metamask/message-manager@10.0.2` (patch) - `@metamask/network-controller@20.1.0` (minor) - `@metamask/notification-services-controller@0.2.0` (minor) - `@metamask/polling-controller@9.0.1` (patch) - `@metamask/preferences-controller@13.0.1` (patch) - `@metamask/polling-controller@9.0.1` (patch) - `@metamask/profile-sync-controller@0.2.0` (minor) - `@metamask/queued-request-controller@4.0.0` (major) - `@metamask/selected-network-controller@17.0.0` (major) - `@metamask/signature-controller@18.0.1` (patch) - `@metamask/transaction-controller@35.0.1` (patch) - `@metamask/user-operation-controller@14.0.1` (patch) - Closes #3651 - Unblocks new releases in core. - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate --------- Co-authored-by: Elliot Winkler <elliot.winkler@gmail.com> Co-authored-by: Mark Stacey <markjstacey@gmail.com>
Explanation
This is the release candidate for
v180.0.0:@metamask/accounts-controller@18.0.0(major)@metamask/assets-controllers@37.0.0(major)@metamask/chain-controllers@0.1.1(patch)@metamask/ens-controller@13.0.1(patch)@metamask/eth-json-rpc-provider@4.1.2(patch)@metamask/gas-fee-controller@19.0.1(patch)@metamask/keyring-controller@17.1.2(patch)@metamask/message-manager@10.0.2(patch)@metamask/network-controller@20.1.0(minor)@metamask/notification-services-controller@0.2.0(minor)@metamask/polling-controller@9.0.1(patch)@metamask/preferences-controller@13.0.1(patch)@metamask/polling-controller@9.0.1(patch)@metamask/profile-sync-controller@0.2.0(minor)@metamask/queued-request-controller@4.0.0(major)@metamask/selected-network-controller@17.0.0(major)@metamask/signature-controller@18.0.1(patch)@metamask/transaction-controller@35.0.1(patch)@metamask/user-operation-controller@14.0.1(patch)References
Checklist