Skip to content

Release/1179.0.0 - #9791

Merged
ccharly merged 2 commits into
mainfrom
release/1179.0.0
Aug 5, 2026
Merged

Release/1179.0.0#9791
ccharly merged 2 commits into
mainfrom
release/1179.0.0

Conversation

@ccharly

@ccharly ccharly commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Explanation

Release of multiple controllers to re-align all new accounts major deps.

References

N/A

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • 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
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Medium Risk
Touches many packages that depend on keyring and accounts controllers; @metamask/money-account-controller@1.0.0 is a breaking release for consumers relying on money-account transaction signing.

Overview
Monorepo release 1179.0.0 that publishes version bumps and changelog entries across many @metamask/* packages so dependents pick up aligned account/keyring stack versions.

The diff is almost entirely semver bumps, package.json dependency range updates, yarn.lock, and changelog link fixes—no new application logic in this PR. Common bumps propagated through the tree include @metamask/keyring-controller 27.1.0 → 27.1.1, @metamask/accounts-controller 39.0.6 → 39.0.7, @metamask/multichain-account-service 13.0.0 → 13.0.1, @metamask/network-enablement-controller 6.0.2 → 6.0.3, and @metamask/multichain-network-controller 3.2.2 → 3.2.3.

Notable released versions in this cut include @metamask/money-account-controller 1.0.0 (changelog documents the breaking removal of eth_signTransaction for money accounts), plus patch/minor releases such as account-tree-controller 7.6.1, client-utils 2.0.1, earn-controller 12.2.4, and several others listed in their changelogs under this release PR (#9791).

Reviewed by Cursor Bugbot for commit e7c5ec5. Bugbot is set up for automated code reviews on this repo. Configure here.

@ccharly ccharly changed the title Update Release 1179.0.0 Release/1179.0.0 Aug 5, 2026
@ccharly

ccharly commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

@metamaskbot update-changelogs

@ccharly

ccharly commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

Adding DO-NOT-MERGE so we can wait for the previous release to be published first

@metamask-ci

This comment has been minimized.

@ccharly

ccharly commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

@metamaskbot update-changelogs

@metamask-ci

This comment has been minimized.

@ccharly
ccharly marked this pull request as ready for review August 5, 2026 11:23
@ccharly
ccharly requested review from a team as code owners August 5, 2026 11:23
@ccharly
ccharly temporarily deployed to default-branch August 5, 2026 11:23 — with GitHub Actions Inactive
@ccharly
ccharly temporarily deployed to default-branch August 5, 2026 11:24 — with GitHub Actions Inactive
@metamask-ci

metamask-ci Bot commented Aug 5, 2026

Copy link
Copy Markdown

✅ No changelog changes needed.

@ccharly
ccharly added this pull request to the merge queue Aug 5, 2026
Merged via the queue into main with commit f6ab836 Aug 5, 2026
221 of 222 checks passed
@ccharly
ccharly deleted the release/1179.0.0 branch August 5, 2026 11:38
@maxime-oe maxime-oe mentioned this pull request Aug 5, 2026
4 tasks
pull Bot pushed a commit to Reality2byte/core that referenced this pull request Aug 5, 2026
## Explanation

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## [111.1.0]

### Added

- Add `offhours` field to `TokenRwaData` and `RwaTokenData` types to
support off-hours RWA trading windows
([MetaMask#9792](MetaMask#9792))
- `offhours.nextOpen`: ISO-8601 datetime when the next off-hours window
opens
- `offhours.nextClose`: ISO-8601 datetime when the next off-hours window
closes
- Field is only present when the asset's source reports off-hours
tradability; absence means off-hours trading is not supported
- Add 0G (`16661`/`0x4115`) entries in `multicall.ts` and `codefi-v2.ts`
([MetaMask#9760](MetaMask#9760))

### Changed

- Bump `@metamask/account-tree-controller` from `^7.6.0` to `^7.6.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/accounts-controller` from `^39.0.6` to `^39.0.7`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/keyring-controller` from `^27.1.0` to `^27.1.1`
([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/multichain-account-service` from `^13.0.0` to
`^13.0.1` ([MetaMask#9791](MetaMask#9791))
- Bump `@metamask/network-enablement-controller` from `^6.0.2` to
`^6.0.3` ([MetaMask#9791](MetaMask#9791))

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] 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

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Version and dependency-only changes with no runtime code in this diff;
risk is limited to consumers picking up the new assets-controllers minor
release.
> 
> **Overview**
> **Monorepo release `1180.0.0`** bumps the root
`@metamask/core-monorepo` version and cuts
**`@metamask/assets-controllers` `111.1.0`**, with changelog entries
moved from `[Unreleased]` into the new `111.1.0` section (RWA `offhours`
on `TokenRwaData` / `RwaTokenData`, 0G chain in `multicall.ts` /
`codefi-v2.ts`, plus prior dependency bumps).
> 
> **Downstream packages** now depend on `@metamask/assets-controllers`
**`^111.1.0`** instead of `^111.0.0`: `@metamask/assets-controller`,
`@metamask/bridge-controller`, and
`@metamask/transaction-pay-controller`, with matching changelog notes
and **`yarn.lock`** updates.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
e4fffd7. 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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants