fix(deps): update dependency @ethersproject/address to ^5.8.0 - #10478
Merged
Merged
Conversation
cryptodev-2s
previously approved these changes
Sep 25, 2026
cryptodev-2s
enabled auto-merge
September 25, 2026 15:10
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 25, 2026
metamask-ci
Bot
force-pushed
the
renovate/ethersproject-address-5.x
branch
from
September 25, 2026 19:03
73297cb to
4707c39
Compare
cryptodev-2s
previously approved these changes
Sep 26, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 26, 2026
1 of 4 tasks
metamask-ci
Bot
force-pushed
the
renovate/ethersproject-address-5.x
branch
from
September 27, 2026 06:15
64c8633 to
05109a0
Compare
cryptodev-2s
previously approved these changes
Sep 27, 2026
metamask-ci
Bot
force-pushed
the
renovate/ethersproject-address-5.x
branch
from
September 28, 2026 06:19
52621db to
13ef744
Compare
cryptodev-2s
approved these changes
Sep 28, 2026
FrederikBolding
pushed a commit
that referenced
this pull request
Sep 28, 2026
This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@ethersproject/address](https://redirect.github.com/ethers-io/ethers.js) ([source](https://redirect.github.com/ethers-io/ethers.js/tree/HEAD/packages/address)) | [`^5.7.0` → `^5.8.0`](https://renovatebot.com/diffs/npm/@ethersproject%2faddress/5.8.0/5.8.0) |  |  | --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMDYuMCIsInVwZGF0ZWRJblZlciI6IjQ0LjEwNi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Patch-level ethers.js dependency bump with no logic changes; address helpers should remain API-compatible within the 5.x line. > > **Overview** > Updates **`@ethersproject/address`** from **`^5.7.0`** to **`^5.8.0`** in **`assets-controllers`** and **`bridge-controller`**, with matching **`yarn.lock`** resolutions and **Unreleased** changelog notes in both packages. > > These controllers already rely on this library for address checks and normalization (e.g. **`isAddress`**, **`getAddress`**); the change is dependency alignment only, with no application code edits in the diff. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit a6054ea. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: metamask-ci[bot] <271559518+metamask-ci[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
FrederikBolding
pushed a commit
that referenced
this pull request
Sep 28, 2026
## Explanation `@ethersproject` has 11 packages here and they all ship from one repository at one version, so the 5.8.0 release produced #10478, #10481, #10482, #10483 and #10484, each bumping the same manifests and writing into the same changelogs. They cannot be merged independently without conflicting. `config:recommended` already pulls in `group:monorepos`, but that works off Renovate's own monorepo data, which has no `ethers` entry, nor most of ours. So instead of listing scopes, this groups by the repository a package is published from, which is the thing that actually decides whether releases move together. `groupName` supports templating and `sourceRepoSlug` is available, so it is one rule for every dependency. That is also more accurate than grouping by npm scope. `@noble` would have been wrong as a scope group, since `noble-hashes`, `noble-curves` and `noble-ciphers` are three separate repositories, and this splits them correctly without being told. Two exclusions: - `@types`, because DefinitelyTyped is a single repository holding 21 unrelated libraries. The two that do belong with something else, `@types/jest` and `@types/react`, are already paired with their runtime packages by `group:jestPlusTypes` and `group:react`. - `@metamask`, because grouping it would touch most of the monorepo in one pull request. The `{{#if}}` fallback is load bearing rather than decoration. A package with no `sourceUrl` gets an empty `groupName`, and `hasGroupName` only tests for `null`, so without it every such package would collapse into one nameless group. Validated with `renovate-config-validator --strict`. Renovate will supersede the five open `@ethersproject` pull requests with a single grouped one on the next run. ## References Follows #10451. Part of WPC-1161. ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
pull Bot
pushed a commit
to Reality2byte/core
that referenced
this pull request
Sep 28, 2026
## Explanation `@ethersproject` has 11 packages here and they all ship from one repository at one version, so the 5.8.0 release produced MetaMask#10478, MetaMask#10481, MetaMask#10482, MetaMask#10483 and MetaMask#10484, each bumping the same manifests and writing into the same changelogs. They cannot be merged independently without conflicting. `config:recommended` already pulls in `group:monorepos`, but that works off Renovate's own monorepo data, which has no `ethers` entry, nor most of ours. So instead of listing scopes, this groups by the repository a package is published from, which is the thing that actually decides whether releases move together. `groupName` supports templating and `sourceRepoSlug` is available, so it is one rule for every dependency. That is also more accurate than grouping by npm scope. `@noble` would have been wrong as a scope group, since `noble-hashes`, `noble-curves` and `noble-ciphers` are three separate repositories, and this splits them correctly without being told. Two exclusions: - `@types`, because DefinitelyTyped is a single repository holding 21 unrelated libraries. The two that do belong with something else, `@types/jest` and `@types/react`, are already paired with their runtime packages by `group:jestPlusTypes` and `group:react`. - `@metamask`, because grouping it would touch most of the monorepo in one pull request. The `{{#if}}` fallback is load bearing rather than decoration. A package with no `sourceUrl` gets an empty `groupName`, and `hasGroupName` only tests for `null`, so without it every such package would collapse into one nameless group. Validated with `renovate-config-validator --strict`. Renovate will supersede the five open `@ethersproject` pull requests with a single grouped one on the next run. ## References Follows MetaMask#10451. Part of WPC-1161. ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^5.7.0→^5.8.0Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
Note
Low Risk
Patch-level ethers.js dependency bump with no logic changes; address helpers should remain API-compatible within the 5.x line.
Overview
Updates
@ethersproject/addressfrom^5.7.0to^5.8.0inassets-controllersandbridge-controller, with matchingyarn.lockresolutions and Unreleased changelog notes in both packages.These controllers already rely on this library for address checks and normalization (e.g.
isAddress,getAddress); the change is dependency alignment only, with no application code edits in the diff.Reviewed by Cursor Bugbot for commit a6054ea. Bugbot is set up for automated code reviews on this repo. Configure here.