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

Version v7.7.9 RC #8444

Merged
merged 18 commits into from
May 4, 2020
Merged

Version v7.7.9 RC #8444

merged 18 commits into from
May 4, 2020

Conversation

metamaskbot
Copy link
Collaborator

@metamaskbot metamaskbot commented Apr 28, 2020

📦 🚀

Changelog:

  • #8446: Fix popup not opening
  • #8449: Skip adding history entry for empty txMeta diffs
  • #8447: Delete Dai/Sai migration notification
  • #8460: Update deposit copy for Wyre
  • #8458: Snapshot txMeta without cloning history
  • #8459: Fix method registry initialization
  • #8455: Add Dai/Sai to currency display
  • #8461: Prevent network switch upon close of network timeout overlay
  • #8457: Add INR currency option
  • #8462: Fix display of Kovan and Rinkeby chain IDs
  • #8465: Use ethereum-ens-network-map for network support
  • #8463: Update deprecated Etherscam link
  • #8474: Only update pending transactions upon block update
  • #8476: Update eth-contract-metadata
  • #8509: Fix Tohen Typo

@Gudahtt Gudahtt marked this pull request as draft April 28, 2020 15:53
@metamaskbot
Copy link
Collaborator Author

Builds ready [a7911ce]

This is a backport of #8314. Here's the original description:

MetaMask would sometimes get into a state where the notification popup
would never open. This could happen if the notification window was
closed shortly after being opened. After this happened, no popups would
show up until after the extension was reset.

This was happening because the background thought the popup was already
open. The variable it uses to track whether the popup was open or not
was being set to `true` immediately after the background asked the
browser to open a new window, before a handler was attached that could
respond to the window being closed.

Removing this line seems to solve the problem.

This line was added originally in #5437, which dealt with batch
transactions. Batches of transactions seem to work just fine without
this line though (from local testing), and I can't think of why this
would be required.

Closes #7051
@metamaskbot
Copy link
Collaborator Author

Builds ready [2a51399]

@metamaskbot
Copy link
Collaborator Author

Builds ready [8fb615c]

This backports the deletion of the Dai/Sai migration notification
(#8418). Note that the migration to delete the now unused background
state has not been included, as it is non-essential and would have been
more difficult to backport. The migration to delete the unused state
will be included in the next major release instead.
@metamaskbot
Copy link
Collaborator Author

Builds ready [57fdc03]

Gudahtt and others added 2 commits April 29, 2020 15:17
Backport #7654 to v7.7.9

Co-authored-by: Tyson Malchow <[email protected]>
This is backported to make it easier to backport #7986

Co-authored-by: Whymarrh Whitby <[email protected]>
@metamaskbot
Copy link
Collaborator Author

Builds ready [50b48b7]

Backport #8363 to v7.7.9. Note that this uses `clone` instead of
`cloneDeep`, because `clone` hadn't yet been replaced by `cloneDeep` on
`master`.

Backporting that change as well would have been very disruptive, so
I've updated this to use `clone` instead to minimize conflicts. It is
functionally equivalent.

Co-authored-by: Whymarrh Whitby <[email protected]>
@metamaskbot
Copy link
Collaborator Author

Builds ready [f91bd3a]

Backport #8200 to v7.7.9. Original commit description:

The method registry was being initialized with the global variable
`ethereumProvider` before that variable was set. As a result, the
method registry was falling back to an internally constructed provider
that used the wrong provider URL (an obsolete Infura API). This was
resulting in an error with the message "Project ID not found".

The method registry is now initialized lazily, when it's first needed.
This should be well after the initialization of `ethereumProvider`,
which occurs during the UI initialization.
@metamaskbot
Copy link
Collaborator Author

Builds ready [3dc8387]

)

Backport #7986 onto v7.7.9. The original commit message follows:

With the change from infura to cryptocompare https://github.com/MetaMask/gaba/pull/30/files#diff-50c3c47cc5fa12e5213a6cc900476f41L41-R48 we have numerous conversion rates to go through and add if we like to.

Co-authored-by: Thomas Huang <[email protected]>
@metamaskbot
Copy link
Collaborator Author

Builds ready [361c571]

Gudahtt and others added 5 commits April 29, 2020 18:34
Backport #7673 to v7.7.9.

Co-authored-by: Whymarrh Whitby <[email protected]>
Backport #7464 to v7.7.9

Co-authored-by: Alice Henshaw <[email protected]>
Co-authored-by: Whymarrh Whitby <[email protected]>
@metamaskbot
Copy link
Collaborator Author

Builds ready [2d36d42]

Gudahtt and others added 3 commits April 30, 2020 11:38
…8474)

Backport #8445 to v7.7.9. Original commit description:

* Don't updatePendingTxs outside of block updates

Refs #8377

Reverts 507397f (#5431)

* Check for new block data on unlock

Co-authored-by: Whymarrh Whitby <[email protected]>
@Gudahtt Gudahtt marked this pull request as ready for review April 30, 2020 14:59
@Gudahtt Gudahtt requested review from danjm and Gudahtt as code owners April 30, 2020 14:59
@Gudahtt Gudahtt requested a review from whymarrh as a code owner April 30, 2020 14:59
@metamaskbot
Copy link
Collaborator Author

Builds ready [8d8a17d]

@Gudahtt Gudahtt requested a review from a team April 30, 2020 15:32
tmashuang
tmashuang previously approved these changes May 4, 2020
Backport #7808 to v7.7.9

Co-authored-by: Lenard Frommelt <[email protected]>
tmashuang
tmashuang previously approved these changes May 4, 2020
@metamaskbot
Copy link
Collaborator Author

Builds ready [b81558a]

@tmashuang tmashuang dismissed their stale review May 4, 2020 17:48

Dissmissing review to check for trezor connectivity.

Copy link
Contributor

@tmashuang tmashuang left a comment

Choose a reason for hiding this comment

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

Trezor firmware latest version, at this time, continues to work.

@tmashuang tmashuang merged commit 5e8a80e into master May 4, 2020
@tmashuang tmashuang deleted the Version-v7.7.9 branch May 4, 2020 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants