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

@metamask/[email protected] #767

Closed
wants to merge 3 commits into from
Closed

@metamask/[email protected] #767

wants to merge 3 commits into from

Conversation

rekmarks
Copy link
Member

@rekmarks rekmarks commented Apr 7, 2022

Replaces [email protected] with @metamask/[email protected]. This prevents some messages that appear to have been previously accepted from being signed, so this ought to be a breaking change.

@rekmarks rekmarks changed the title @metamask/[email protected] BREAKING: @metamask/[email protected] Apr 7, 2022
Base automatically changed from @lavamoat/[email protected] to main April 7, 2022 17:44
@rekmarks rekmarks force-pushed the @metamask/eth-sig-util branch from f27ee2b to 27cef8e Compare April 7, 2022 17:45
@rekmarks rekmarks marked this pull request as ready for review April 7, 2022 17:45
@rekmarks rekmarks requested a review from a team as a code owner April 7, 2022 17:45
case SignTypedDataVersion.V4:
return signTypedData_v4(privateKeyBuffer, {
data: JSON.parse(messageParams.data as string),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These JSON.parse calls were removed, but we still need this to be JSON data rather than a string

@Gudahtt Gudahtt changed the title BREAKING: @metamask/[email protected] @metamask/[email protected] Apr 14, 2022
@Gudahtt Gudahtt marked this pull request as draft April 19, 2022 20:50
@Gudahtt
Copy link
Member

Gudahtt commented Apr 19, 2022

Some of the unit tests are failing here because of a mistake made in the typed message schema in eth-sig-util@4. This schema mistake is fixed here: MetaMask/eth-sig-util#243

@Gudahtt
Copy link
Member

Gudahtt commented Apr 21, 2022

The schema mistake has been fixed and published as [email protected]

@mcmire
Copy link
Contributor

mcmire commented Jun 3, 2022

Is this something we need to get into the next release? I'm assuming no since this is still in draft, but just wanted to check.

@legobeat
Copy link
Contributor

This was done in #914

@legobeat legobeat closed this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants