{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":135296009,"defaultBranch":"main","name":"core","ownerLogin":"MetaMask","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2018-05-29T12:55:25.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/11744586?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1716342595.0","currentOid":""},"activityList":{"items":[{"before":"f565d333b6a51643777b729b076920b67177e839","after":"7d25cce146bea00c8af9d67cd892311ca79b1d41","ref":"refs/heads/group-network-configurations-by-chain","pushedAt":"2024-05-22T02:42:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"mcmire","name":"Elliot Winkler","path":"/mcmire","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7371?s=80&v=4"},"commit":{"message":"Group network configurations by chain ID\n\nCurrently, in the client, it is possible to have multiple networks with\ndifferent RPC endpoint URLs representing the same chain. This creates a\nproblem because if all we have is a chain ID, we don't know which URL to\nuse for requests.\n\nTo solve this, we plan on consolidating the UX on the client side such\nthat each network corresponds to exactly one chain. Users can then\nselect which default RPC URL they'd like to use for requests. This\ncommit implements the controller changes necessary to support this UX.\n\nHere are some more details on the changes here:\n\n- The concept of a network configuration has been repurposed such that\n  instead of representing an RPC endpoint, it now represents a whole\n  chain.\n\n  - A network configuration may have multiple RPC endpoints, and\n    one of them must be designated as the default.\n  - Some RPC endpoints are special in that they represent Infura API\n    URLs; these have the same object shape as \"non-Infura\" (custom) RPC\n    endpoints, but the Infura project ID is hidden and injected into the\n    RPC URL when creating the network client.\n  - There is no longer a 1-to-1 relationship between network\n    configuration and network client; rather, the 1-to-1 relationship\n    exists between RPC endpoint and network client. This means that the\n    ID of the network client which is created for an RPC endpoint\n    is stored on that RPC endpoint instead of the whole network\n    configuration.\n\n- The `networkConfigurations` state property has been replaced with\n  `networkConfigurationsByChainId`. This continues to be an object, but\n  the data inside is organized such that network configurations are\n  identified by chain ID instead of network client ID as they were\n  previously.\n\n- The methods `upsertNetworkConfiguration` and\n  `removeNetworkConfiguration` have been removed. These methods always\n  did more than simply add or remove a network configuration; they also\n  updated the registry of network clients. Instead, these methods have\n  been replaced with `addNetwork`, `updateNetwork`, and `removeNetwork`.\n\n  - `addNetwork` creates new network clients for each RPC endpoint in\n    the given network configuration.\n  - `updateNetwork` takes a chain ID referring to a network\n    configuration and a draft version of that network configuration,\n    and adds or removes network clients for added or removed RPC\n    endpoints.\n  - `removeNetwork` takes a chain ID referring to a network\n    configuration and removes the network clients for each of its RPC\n    endpoints.\n\n- In addition, due to the changes to network configuration itself, there\n  are new restrictions on `networkConfigurationsByChainId`, which are\n  validated on initialization and on update. These are:\n\n  - The network controller cannot be initialized with an empty\n    collection of network configurations. This is because there must be\n    a selected network client so that consumers have a provider to use\n    out of the gate.\n  - Consequently, the last network configuration cannot be removed.\n  - The chain ID of a network configuration must match the same chain\n    that it's filed under in `networkConfigurationsByChainId`.\n  - No two network configurations can have the same chain ID.\n  - A RPC endpoint in a network configuration must have a well-formed\n    URL.\n  - A network configuration cannot have duplicate RPC endpoints.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same URL. Equality is currently determined by normalizing URLs\n    as per RFC 3986 and may include data like request headers in the\n    future.\n  - If a network configuration has an Infura RPC endpoint, its chain ID\n    must match the set chain ID of the network configuration.\n    - Changing the chain ID of a network configuration is possible, but\n      any existing Infura RPC endpoint must be replaced with the one\n      that matches the new chain ID.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same network client ID.","shortMessageHtmlLink":"Group network configurations by chain ID"}},{"before":"b9fea2b9e5373ba3fa7609834445198bfd48fe41","after":null,"ref":"refs/heads/dependabot/npm_and_yarn/metamask/action-utils-1.1.1","pushedAt":"2024-05-22T01:49:55.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"legobeat","name":null,"path":"/legobeat","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/109787230?s=80&v=4"}},{"before":"c475090ca2e805f17f54eb560cb095e3e4695efe","after":"cad9c705894da519a50388c620c0d1c3bb310f8e","ref":"refs/heads/main","pushedAt":"2024-05-22T01:49:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"legobeat","name":null,"path":"/legobeat","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/109787230?s=80&v=4"},"commit":{"message":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1 (#4288)","shortMessageHtmlLink":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2302574589\" data-permission-text=\"Title is private\" data-url=\"https://github.com/MetaMask/core/issues/4288\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/MetaMask/core/pull/4288/hovercard\" href=\"https://github.com/MetaMask/core/pull/4288\">#4288</a>)"}},{"before":"2793ca66c6b73b1885d55fc18b046cb34c957f54","after":"b358c99f9bba3e6588114909ecb3cd29826eef35","ref":"refs/heads/231208-typescript-module-resolution","pushedAt":"2024-05-22T01:36:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"MajorLift","name":"Jongsun Suh","path":"/MajorLift","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34228073?s=80&v=4"},"commit":{"message":"stash","shortMessageHtmlLink":"stash"}},{"before":"b8c61c52d01c7be23991667aa5cd0654e706d4d2","after":"2793ca66c6b73b1885d55fc18b046cb34c957f54","ref":"refs/heads/231208-typescript-module-resolution","pushedAt":"2024-05-22T01:29:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"MajorLift","name":"Jongsun Suh","path":"/MajorLift","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34228073?s=80&v=4"},"commit":{"message":"stash","shortMessageHtmlLink":"stash"}},{"before":"ab48428a0bc76f0a61ba58d6ef1173cde17756bf","after":"b8c61c52d01c7be23991667aa5cd0654e706d4d2","ref":"refs/heads/231208-typescript-module-resolution","pushedAt":"2024-05-22T01:13:32.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"MajorLift","name":"Jongsun Suh","path":"/MajorLift","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34228073?s=80&v=4"},"commit":{"message":"Linter fixes","shortMessageHtmlLink":"Linter fixes"}},{"before":"26937bc185ac0f7d1b6fc291ce339ffd337fa774","after":"ab48428a0bc76f0a61ba58d6ef1173cde17756bf","ref":"refs/heads/231208-typescript-module-resolution","pushedAt":"2024-05-22T01:01:57.000Z","pushType":"push","commitsCount":19,"pusher":{"login":"MajorLift","name":"Jongsun Suh","path":"/MajorLift","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34228073?s=80&v=4"},"commit":{"message":"Merge branch 'main' into 231208-typescript-module-resolution","shortMessageHtmlLink":"Merge branch 'main' into 231208-typescript-module-resolution"}},{"before":"3ee422986c7794877f092f2a5d6e6516b9fbf11f","after":"26937bc185ac0f7d1b6fc291ce339ffd337fa774","ref":"refs/heads/231208-typescript-module-resolution","pushedAt":"2024-05-22T00:57:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"MajorLift","name":"Jongsun Suh","path":"/MajorLift","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/34228073?s=80&v=4"},"commit":{"message":"stash","shortMessageHtmlLink":"stash"}},{"before":"5d2a69cd570c1e5b0d25141ea6b5bea764ed70d0","after":"f565d333b6a51643777b729b076920b67177e839","ref":"refs/heads/group-network-configurations-by-chain","pushedAt":"2024-05-21T23:12:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"mcmire","name":"Elliot Winkler","path":"/mcmire","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7371?s=80&v=4"},"commit":{"message":"Group network configurations by chain ID\n\nCurrently, in the client, it is possible to have multiple networks with\ndifferent RPC endpoint URLs representing the same chain. This creates a\nproblem because if all we have is a chain ID, we don't know which URL to\nuse for requests.\n\nTo solve this, we plan on consolidating the UX on the client side such\nthat each network corresponds to exactly one chain. Users can then\nselect which default RPC URL they'd like to use for requests. This\ncommit implements the controller changes necessary to support this UX.\n\nHere are some more details on the changes here:\n\n- The concept of a network configuration has been repurposed such that\n  instead of representing an RPC endpoint, it now represents a whole\n  chain.\n\n  - A network configuration may have multiple RPC endpoints, and\n    one of them must be designated as the default.\n  - Some RPC endpoints are special in that they represent Infura API\n    URLs; these have the same object shape as \"non-Infura\" (custom) RPC\n    endpoints, but the Infura project ID is hidden and injected into the\n    RPC URL when creating the network client.\n  - There is no longer a 1-to-1 relationship between network\n    configuration and network client; rather, the 1-to-1 relationship\n    exists between RPC endpoint and network client. This means that the\n    ID of the network client which is created for an RPC endpoint\n    is stored on that RPC endpoint instead of the whole network\n    configuration.\n\n- The `networkConfigurations` state property has been replaced with\n  `networkConfigurationsByChainId`. This continues to be an object, but\n  the data inside is organized such that network configurations are\n  identified by chain ID instead of network client ID as they were\n  previously.\n\n- The methods `upsertNetworkConfiguration` and\n  `removeNetworkConfiguration` have been removed. These methods always\n  did more than simply add or remove a network configuration; they also\n  updated the registry of network clients. Instead, these methods have\n  been replaced with `addNetwork`, `updateNetwork`, and `removeNetwork`.\n\n  - `addNetwork` creates new network clients for each RPC endpoint in\n    the given network configuration.\n  - `updateNetwork` takes a chain ID referring to a network\n    configuration and a draft version of that network configuration,\n    and adds or removes network clients for added or removed RPC\n    endpoints.\n  - `removeNetwork` takes a chain ID referring to a network\n    configuration and removes the network clients for each of its RPC\n    endpoints.\n\n- In addition, due to the changes to network configuration itself, there\n  are new restrictions on `networkConfigurationsByChainId`, which are\n  validated on initialization and on update. These are:\n\n  - The network controller cannot be initialized with an empty\n    collection of network configurations. This is because there must be\n    a selected network client so that consumers have a provider to use\n    out of the gate.\n  - Consequently, the last network configuration cannot be removed.\n  - No two network configurations can have the same chain ID.\n  - A RPC endpoint in a network configuration must have a well-formed\n    URL.\n  - A network configuration cannot have duplicate RPC endpoints.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same URL. Equality is currently determined by normalizing URLs\n    as per RFC 3986 and may include data like request headers in the\n    future.\n  - If a network configuration has an Infura RPC endpoint, its chain ID\n    must match the set chain ID of the network configuration.\n    - Changing the chain ID of a network configuration is possible, but\n      any existing Infura RPC endpoint must be replaced with the one\n      that matches the new chain ID.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same network client ID.","shortMessageHtmlLink":"Group network configurations by chain ID"}},{"before":"7f4d92b2f841e1600f6a1a4b241ccd50c6bb9974","after":"5d2a69cd570c1e5b0d25141ea6b5bea764ed70d0","ref":"refs/heads/group-network-configurations-by-chain","pushedAt":"2024-05-21T23:10:23.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"mcmire","name":"Elliot Winkler","path":"/mcmire","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/7371?s=80&v=4"},"commit":{"message":"Group network configurations by chain ID\n\nCurrently, in the client, it is possible to have multiple networks with\ndifferent RPC endpoint URLs representing the same chain. This creates a\nproblem because if all we have is a chain ID, we don't know which URL to\nuse for requests.\n\nTo solve this, we plan on consolidating the UX on the client side such\nthat each network corresponds to exactly one chain. Users can then\nselect which default RPC URL they'd like to use for requests. This\ncommit implements the controller changes necessary to support this UX.\n\nHere are some more details on the changes here:\n\n- The concept of a network configuration has been repurposed such that\n  instead of representing an RPC endpoint, it now represents a whole\n  chain.\n\n  - A network configuration may have multiple RPC endpoints, and\n    one of them must be designated as the default.\n  - Some RPC endpoints are special in that they represent Infura API\n    URLs; these have the same object shape as \"non-Infura\" (custom) RPC\n    endpoints, but the Infura project ID is hidden and injected into the\n    RPC URL when creating the network client.\n  - There is no longer a 1-to-1 relationship between network\n    configuration and network client; rather, the 1-to-1 relationship\n    exists between RPC endpoint and network client. This means that the\n    ID of the network client which is created for an RPC endpoint\n    is stored on that RPC endpoint instead of the whole network\n    configuration.\n\n- The `networkConfigurations` state property has been replaced with\n  `networkConfigurationsByChainId`. This continues to be an object, but\n  the data inside is organized such that network configurations are\n  identified by chain ID instead of network client ID as they were\n  previously. ()\n\n- The methods `upsertNetworkConfiguration` and\n  `removeNetworkConfiguration` have been removed. These methods always\n  did more than simply add or remove a network configuration; they also\n  updated the registry of network clients. Instead, these methods have\n  been replaced with `addNetwork`, `updateNetwork`, and `removeNetwork`.\n\n  - `addNetwork` creates new network clients for each RPC endpoint in\n    the given network configuration.\n  - `updateNetwork` takes a chain ID referring to a network\n    configuration and a draft version of that network configuration,\n    and adds or removes network clients for added or removed RPC\n    endpoints.\n  - `removeNetwork` takes a chain ID referring to a network\n    configuration and removes the network clients for each of its RPC\n    endpoints.\n\n- In addition, due to the changes to network configuration itself, there\n  are new restrictions on `networkConfigurationsByChainId`, which are\n  validated on initialization and on update. These are:\n\n  - The network controller cannot be initialized with an empty\n    collection of network configurations. This is because there must be\n    a selected network client so that consumers have a provider to use\n    out of the gate.\n  - Consequently, the last network configuration cannot be removed.\n  - No two network configurations can have the same chain ID.\n  - A RPC endpoint in a network configuration must have a well-formed\n    URL.\n  - A network configuration cannot have duplicate RPC endpoints.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same URL. Equality is currently determined by normalizing URLs\n    as per RFC 3986 and may include data like request headers in the\n    future.\n  - If a network configuration has an Infura RPC endpoint, its chain ID\n    must match the set chain ID of the network configuration.\n    - Changing the chain ID of a network configuration is possible, but\n      any existing Infura RPC endpoint must be replaced with the one\n      that matches the new chain ID.\n  - No two RPC endpoints (regardless of network configuration) can have\n    the same network client ID.","shortMessageHtmlLink":"Group network configurations by chain ID"}},{"before":"c5e3538033889e780a1b34c6b51728ef6920c8e7","after":"b9fea2b9e5373ba3fa7609834445198bfd48fe41","ref":"refs/heads/dependabot/npm_and_yarn/metamask/action-utils-1.1.1","pushedAt":"2024-05-21T23:07:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1\n\nBumps [@metamask/action-utils](https://github.com/MetaMask/action-utils) from 1.0.0 to 1.1.1.\n- [Release notes](https://github.com/MetaMask/action-utils/releases)\n- [Changelog](https://github.com/MetaMask/action-utils/blob/v1.1.1/CHANGELOG.md)\n- [Commits](https://github.com/MetaMask/action-utils/compare/v1.0.0...v1.1.1)\n\n---\nupdated-dependencies:\n- dependency-name: \"@metamask/action-utils\"\n  dependency-type: indirect\n  update-type: version-update:semver-minor\n...\n\nSigned-off-by: dependabot[bot] <support@github.com>","shortMessageHtmlLink":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1"}},{"before":"5d29965b9d2a809748323fd9d0e1e9e945b6f569","after":null,"ref":"refs/heads/dependabot/npm_and_yarn/metamask/post-message-stream-8.1.0","pushedAt":"2024-05-21T23:05:34.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"}},{"before":"d9cae1eac77aa10b4aef81973d6ef3c40275f4ad","after":"c475090ca2e805f17f54eb560cb095e3e4695efe","ref":"refs/heads/main","pushedAt":"2024-05-21T23:05:33.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"chore(deps): bump @metamask/post-message-stream from 8.0.0 to 8.1.0 (#4296)","shortMessageHtmlLink":"chore(deps): bump @metamask/post-message-stream from 8.0.0 to 8.1.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2308248877\" data-permission-text=\"Title is private\" data-url=\"https://github.com/MetaMask/core/issues/4296\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/MetaMask/core/pull/4296/hovercard\" href=\"https://github.com/MetaMask/core/pull/4296\">#…</a>"}},{"before":null,"after":"622a8e898ec7daf9eb3e9525e47eec58a16a59ba","ref":"refs/heads/fix/replace-metafi-metaswap-subdomains","pushedAt":"2024-05-21T22:46:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cryptodev-2s","name":null,"path":"/cryptodev-2s","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/109512101?s=80&v=4"},"commit":{"message":"fix: Migrate API usage from *.metafi & *.metaswap subdomains to *.cx.metamask.io","shortMessageHtmlLink":"fix: Migrate API usage from *.metafi &amp; *.metaswap subdomains to *.cx.…"}},{"before":"c3db5cb35c10f8913ba14c30890c2a32f3446fd7","after":"a4953ae2e763f2432a4a1c5c0c0b13149bcb9592","ref":"refs/heads/feat/nonevm-rates","pushedAt":"2024-05-21T22:32:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"gantunesr","name":"Gustavo Antunes","path":"/gantunesr","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17601467?s=80&v=4"},"commit":{"message":"docs: update README","shortMessageHtmlLink":"docs: update README"}},{"before":"b8c5bf2e6a851572e52331115b27db4198f8aa93","after":"c3db5cb35c10f8913ba14c30890c2a32f3446fd7","ref":"refs/heads/feat/nonevm-rates","pushedAt":"2024-05-21T22:28:44.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"gantunesr","name":"Gustavo Antunes","path":"/gantunesr","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17601467?s=80&v=4"},"commit":{"message":"test: increase coverage","shortMessageHtmlLink":"test: increase coverage"}},{"before":"a6b2b82f094082b45c61fe11a712471445cda7fa","after":"5d29965b9d2a809748323fd9d0e1e9e945b6f569","ref":"refs/heads/dependabot/npm_and_yarn/metamask/post-message-stream-8.1.0","pushedAt":"2024-05-21T22:18:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"---\nupdated-dependencies:\n- dependency-name: \"@metamask/post-message-stream\"\n  dependency-type: indirect\n  update-type: version-update:semver-minor\n...\n\nSigned-off-by: dependabot[bot] <support@github.com>","shortMessageHtmlLink":"---"}},{"before":"3083d09ec5b1cb055d4bbde1b565dc29245ec85a","after":"c5e3538033889e780a1b34c6b51728ef6920c8e7","ref":"refs/heads/dependabot/npm_and_yarn/metamask/action-utils-1.1.1","pushedAt":"2024-05-21T22:18:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"dependabot[bot]","name":null,"path":"/apps/dependabot","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/29110?s=80&v=4"},"commit":{"message":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1\n\nBumps [@metamask/action-utils](https://github.com/MetaMask/action-utils) from 1.0.0 to 1.1.1.\n- [Release notes](https://github.com/MetaMask/action-utils/releases)\n- [Changelog](https://github.com/MetaMask/action-utils/blob/v1.1.1/CHANGELOG.md)\n- [Commits](https://github.com/MetaMask/action-utils/compare/v1.0.0...v1.1.1)\n\n---\nupdated-dependencies:\n- dependency-name: \"@metamask/action-utils\"\n  dependency-type: indirect\n  update-type: version-update:semver-minor\n...\n\nSigned-off-by: dependabot[bot] <support@github.com>","shortMessageHtmlLink":"chore(deps): bump @metamask/action-utils from 1.0.0 to 1.1.1"}},{"before":"146d0151700cd8d8533593d90c92b0d927c271d6","after":null,"ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T22:15:49.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"}},{"before":"9ef4b26ac44fbf8c8d8a2ef2f75a4eebf609f3bb","after":"d9cae1eac77aa10b4aef81973d6ef3c40275f4ad","ref":"refs/heads/main","pushedAt":"2024-05-21T22:15:48.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"Release 153.0.0 (#4300)\n\n## Explanation\r\n\r\n<!--\r\nThanks for your contribution! Take a moment to answer these questions so\r\nthat reviewers have the information they need to properly understand\r\nyour changes:\r\n\r\n* What is the current state of things and why does it need to change?\r\n* What is the solution your changes offer and how does it work?\r\n* Are there any changes whose purpose might not obvious to those\r\nunfamiliar with the domain?\r\n* If your primary goal was to update one package but you found you had\r\nto update another one along the way, why did you do so?\r\n* If you had to upgrade a dependency, why did you do so?\r\n-->\r\n\r\n## References\r\n\r\n<!--\r\nAre there any issues that this pull request is tied to? Are there other\r\nlinks that reviewers should consult to understand these changes better?\r\n\r\nFor example:\r\n\r\n* Fixes #12345\r\n* Related to #67890\r\n-->\r\n\r\n## Changelog\r\n\r\n<!--\r\nIf you're making any consumer-facing changes, list those changes here as\r\nif you were updating a changelog, using the template below as a guide.\r\n\r\n(CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or\r\nFIXED. For security-related issues, follow the Security Advisory\r\nprocess.)\r\n\r\nPlease take care to name the exact pieces of the API you've added or\r\nchanged (e.g. types, interfaces, functions, or methods).\r\n\r\nIf there are any breaking changes, make sure to offer a solution for\r\nconsumers to follow once they upgrade to the changes.\r\n\r\nFinally, if you're only making changes to development scripts or tests,\r\nyou may replace the template below with \"None\".\r\n-->\r\n\r\n### `@metamask/package-a`\r\n\r\n- **<CATEGORY>**: Your change here\r\n- **<CATEGORY>**: Your change here\r\n\r\n### `@metamask/package-b`\r\n\r\n- **<CATEGORY>**: Your change here\r\n- **<CATEGORY>**: Your change here\r\n\r\n## Checklist\r\n\r\n- [ ] I've updated the test suite for new or updated code as appropriate\r\n- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or\r\nupdated code as appropriate\r\n- [ ] I've highlighted breaking changes using the \"BREAKING\" category\r\nabove as appropriate","shortMessageHtmlLink":"Release 153.0.0 (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2309119052\" data-permission-text=\"Title is private\" data-url=\"https://github.com/MetaMask/core/issues/4300\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/MetaMask/core/pull/4300/hovercard\" href=\"https://github.com/MetaMask/core/pull/4300\">#4300</a>)"}},{"before":"db88f1a5f7c26a5831133cec2b3c3f651c916b10","after":"146d0151700cd8d8533593d90c92b0d927c271d6","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:58:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"chore: update yarn lock","shortMessageHtmlLink":"chore: update yarn lock"}},{"before":"e2b092a78cda8a83033c402c35ae01eca32f93d2","after":"b8c5bf2e6a851572e52331115b27db4198f8aa93","ref":"refs/heads/feat/nonevm-rates","pushedAt":"2024-05-21T21:47:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"gantunesr","name":"Gustavo Antunes","path":"/gantunesr","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17601467?s=80&v=4"},"commit":{"message":"docs: update types","shortMessageHtmlLink":"docs: update types"}},{"before":"c4a24cefb0b93eb47eaeaa4ca901bef741893bee","after":"db88f1a5f7c26a5831133cec2b3c3f651c916b10","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:41:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"chore: uptick package","shortMessageHtmlLink":"chore: uptick package"}},{"before":"155ab86804162a64859a55ec90009c7126b20749","after":"c4a24cefb0b93eb47eaeaa4ca901bef741893bee","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:38:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"docs: categorize commits","shortMessageHtmlLink":"docs: categorize commits"}},{"before":"7a8fd4e27f034cf06bf093d3211f66f2c1fe725e","after":"e2b092a78cda8a83033c402c35ae01eca32f93d2","ref":"refs/heads/feat/nonevm-rates","pushedAt":"2024-05-21T21:30:41.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"gantunesr","name":"Gustavo Antunes","path":"/gantunesr","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17601467?s=80&v=4"},"commit":{"message":"refactor: withLock","shortMessageHtmlLink":"refactor: withLock"}},{"before":"2d8b8dda0dd87a037b3e04047dae40862e8b69cc","after":"155ab86804162a64859a55ec90009c7126b20749","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:26:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"docs: update categorize commits","shortMessageHtmlLink":"docs: update categorize commits"}},{"before":"6d4107be2a9d052a964bc7e2dd3bfcccce16b2dc","after":"2d8b8dda0dd87a037b3e04047dae40862e8b69cc","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:15:05.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"Update Release 153.0.0","shortMessageHtmlLink":"Update Release 153.0.0"}},{"before":"04a3684063b4acaed2549c3270dfd9f43484f3e1","after":"6d4107be2a9d052a964bc7e2dd3bfcccce16b2dc","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:12:17.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"Initialize Release 153.0.0","shortMessageHtmlLink":"Initialize Release 153.0.0"}},{"before":"e44b3f50c680f323adecea98703abefb42e635f2","after":"04a3684063b4acaed2549c3270dfd9f43484f3e1","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:10:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"Update Release 153.0.0","shortMessageHtmlLink":"Update Release 153.0.0"}},{"before":null,"after":"e44b3f50c680f323adecea98703abefb42e635f2","ref":"refs/heads/release/153.0.0","pushedAt":"2024-05-21T21:09:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"BZahory","name":"Bilal","path":"/BZahory","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/44588480?s=80&v=4"},"commit":{"message":"Update Release 153.0.0","shortMessageHtmlLink":"Update Release 153.0.0"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEUHSHYAA","startCursor":null,"endCursor":null}},"title":"Activity · MetaMask/core"}