Skip to content
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

Update metamask/user-operation-controller to version 19.0.0 #28495

Open
metamaskbot opened this issue Nov 15, 2024 · 3 comments · May be fixed by #28781
Open

Update metamask/user-operation-controller to version 19.0.0 #28495

metamaskbot opened this issue Nov 15, 2024 · 3 comments · May be fixed by #28781
Assignees
Labels
team-confirmations Push issues to confirmations team team-wallet-framework

Comments

@metamaskbot
Copy link
Collaborator

metamaskbot commented Nov 15, 2024

Please update metamask/user-operation-controller to version 19.0.0

@metamaskbot metamaskbot added the team-confirmations Push issues to confirmations team label Nov 15, 2024
@pedronfigueiredo
Copy link
Contributor

The update from v 21 to 22 is due to an update to the keyring controller MetaMask/core#4845.

In other to respect the peer dependencies, these need to updated at the same time as the keyring controller is updated to v 18.

@pedronfigueiredo pedronfigueiredo added team-wallet-framework team-confirmations Push issues to confirmations team and removed team-confirmations Push issues to confirmations team labels Nov 15, 2024
@pedronfigueiredo
Copy link
Contributor

Our team needs to update this controller to version 16

@digiwand digiwand changed the title Update metamask/user-operation-controller to version 18.0.0 Update metamask/user-operation-controller to version 19.0.0 Nov 22, 2024
@digiwand
Copy link
Contributor

Updated ticket to upgrade to 19 instead of 18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-confirmations Push issues to confirmations team team-wallet-framework
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants