@metamask-previews/profile-sync-controller 27.0.0-preview-58cfb208 → 27.0.0-preview-fe83443
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/package.json +4 -7
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
### Changed
|
|
11
|
+
|
|
12
|
+
- Move peer dependencies for controller and service packages to direct dependencies ([#7209](https://github.com/MetaMask/core/pull/7209))
|
|
13
|
+
- The dependencies moved are:
|
|
14
|
+
- `@metamask/address-book-controller` (^7.0.1)
|
|
15
|
+
- `@metamask/keyring-controller` (^25.0.0)
|
|
16
|
+
- `@metamask/snaps-controllers` (^14.0.1)
|
|
17
|
+
- In clients, it is now possible for multiple versions of these packages to exist in the dependency tree.
|
|
18
|
+
- For example, this scenario would be valid: a client relies on `@metamask/controller-a` 1.0.0 and `@metamask/controller-b` 1.0.0, and `@metamask/controller-b` depends on `@metamask/controller-a` 1.1.0.
|
|
19
|
+
- Note, however, that the versions specified in the client's `package.json` always "win", and you are expected to keep them up to date so as not to break controller and service intercommunication.
|
|
20
|
+
|
|
10
21
|
## [27.0.0]
|
|
11
22
|
|
|
12
23
|
### Changed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@metamask-previews/profile-sync-controller",
|
|
3
|
-
"version": "27.0.0-preview-
|
|
3
|
+
"version": "27.0.0-preview-fe83443",
|
|
4
4
|
"description": "The profile sync helps developers synchronize data across multiple clients and devices in a privacy-preserving way. All data saved in the user storage database is encrypted client-side to preserve privacy. The user storage provides a modular design, giving developers the flexibility to construct and manage their storage spaces in a way that best suits their needs",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"MetaMask",
|
|
@@ -101,8 +101,11 @@
|
|
|
101
101
|
"test:watch": "NODE_OPTIONS=--experimental-vm-modules jest --watch"
|
|
102
102
|
},
|
|
103
103
|
"dependencies": {
|
|
104
|
+
"@metamask/address-book-controller": "^7.0.1",
|
|
104
105
|
"@metamask/base-controller": "^9.0.0",
|
|
106
|
+
"@metamask/keyring-controller": "^25.0.0",
|
|
105
107
|
"@metamask/messenger": "^0.3.0",
|
|
108
|
+
"@metamask/snaps-controllers": "^14.0.1",
|
|
106
109
|
"@metamask/snaps-sdk": "^9.0.0",
|
|
107
110
|
"@metamask/snaps-utils": "^11.0.0",
|
|
108
111
|
"@metamask/utils": "^11.8.1",
|
|
@@ -115,13 +118,10 @@
|
|
|
115
118
|
"devDependencies": {
|
|
116
119
|
"@lavamoat/allow-scripts": "^3.0.4",
|
|
117
120
|
"@lavamoat/preinstall-always-fail": "^2.1.0",
|
|
118
|
-
"@metamask/address-book-controller": "^7.0.1",
|
|
119
121
|
"@metamask/auto-changelog": "^3.4.4",
|
|
120
122
|
"@metamask/keyring-api": "^21.0.0",
|
|
121
|
-
"@metamask/keyring-controller": "^25.0.0",
|
|
122
123
|
"@metamask/keyring-internal-api": "^9.0.0",
|
|
123
124
|
"@metamask/providers": "^22.1.0",
|
|
124
|
-
"@metamask/snaps-controllers": "^14.0.1",
|
|
125
125
|
"@ts-bridge/cli": "^0.6.4",
|
|
126
126
|
"@types/jest": "^27.4.1",
|
|
127
127
|
"deepmerge": "^4.2.2",
|
|
@@ -136,10 +136,7 @@
|
|
|
136
136
|
"webextension-polyfill": "^0.12.0"
|
|
137
137
|
},
|
|
138
138
|
"peerDependencies": {
|
|
139
|
-
"@metamask/address-book-controller": "^7.0.1",
|
|
140
|
-
"@metamask/keyring-controller": "^25.0.0",
|
|
141
139
|
"@metamask/providers": "^22.0.0",
|
|
142
|
-
"@metamask/snaps-controllers": "^14.0.0",
|
|
143
140
|
"webextension-polyfill": "^0.10.0 || ^0.11.0 || ^0.12.0"
|
|
144
141
|
},
|
|
145
142
|
"engines": {
|