-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Jl/caip multichain/cleanup middleware destroy #28751
Jl/caip multichain/cleanup middleware destroy #28751
Conversation
@metamaskbot update-policies |
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@json-schema-tools/[email protected], npm/@metamask-previews/[email protected] |
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
Builds ready [81867db]
Page Load Metrics (1783 ± 67 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
…n/cleanup-middleware-destroy
Builds ready [0f0bb96]
Page Load Metrics (1709 ± 63 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
…n/cleanup-middleware-destroy
…n/cleanup-middleware-destroy
…n/cleanup-middleware-destroy
Builds ready [3005665]
Page Load Metrics (1659 ± 87 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
…try (#4984) ## Explanation Ensures that the subscription entry for a subscription is removed when the middleware is destroyed ## References Related: MetaMask/metamask-extension#28751 ## Changelog <!-- If you're making any consumer-facing changes, list those changes here as if you were updating a changelog, using the template below as a guide. (CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or FIXED. For security-related issues, follow the Security Advisory process.) Please take care to name the exact pieces of the API you've added or changed (e.g. types, interfaces, functions, or methods). If there are any breaking changes, make sure to offer a solution for consumers to follow once they upgrade to the changes. Finally, if you're only making changes to development scripts or tests, you may replace the template below with "None". --> ### `@metamask/package-a` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ### `@metamask/package-b` - **<CATEGORY>**: Your change here - **<CATEGORY>**: Your change here ## 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
Description
Related issues
Core: MetaMask/core#4984
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist