-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat: increase version of remote-feature-flag-controller to 4.0.0 #24211
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
Conversation
|
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. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsThis PR upgrades @metamask/remote-feature-flag-controller from v3.1.0 to v4.0.0 - a MAJOR version bump. This controller is a critical core dependency that:
Given this is a major version upgrade of a controller that gates features across the entire application, any regression could disable or break multiple features. All test tags should be run to ensure comprehensive coverage. |
sethkfman
left a comment
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
|



Description
Bumping version of remote-feature-flag-controller to support independent A/B tests introduced in:
Changelog
CHANGELOG entry:
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Bumps
@metamask/remote-feature-flag-controllerto 4.0.0 and refreshes lockfile, updating related@metamask/utilsand@metamask/controller-utilsversions.@metamask/remote-feature-flag-controllerfrom^3.1.0to^4.0.0inpackage.json.yarn.lockresolutions accordingly, including@metamask/utilsto11.9.0and@metamask/controller-utilsto11.17.0.Written by Cursor Bugbot for commit 8a5dc27. This will update automatically on new commits. Configure here.