Skip to content

Release/895.0.0#8359

Merged
maxime-oe merged 6 commits intomainfrom
release/895.0.0
Apr 1, 2026
Merged

Release/895.0.0#8359
maxime-oe merged 6 commits intomainfrom
release/895.0.0

Conversation

@maxime-oe
Copy link
Copy Markdown
Contributor

@maxime-oe maxime-oe commented Apr 1, 2026

Explanation

References

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
Mostly release bookkeeping (version bumps, dependency bumps, lockfile updates), but it propagates @metamask/assets-controller@4.0.0 and @metamask/transaction-controller@64.0.0 which include breaking changes that consumers must be compatible with.

Overview
Bumps the monorepo version to 895.0.0 and rolls forward multiple workspace package versions, updating their CHANGELOG.md entries accordingly.

Updates inter-package dependencies to newer releases (notably @metamask/transaction-controller to 64.0.0, @metamask/assets-controller to 4.0.0, and related controller packages), and refreshes yarn.lock to match.

Written by Cursor Bugbot for commit fc4377c. This will update automatically on new commits. Configure here.

@maxime-oe maxime-oe marked this pull request as ready for review April 1, 2026 13:39
@maxime-oe maxime-oe requested review from a team as code owners April 1, 2026 13:39
cryptodev-2s
cryptodev-2s previously approved these changes Apr 1, 2026
@maxime-oe maxime-oe enabled auto-merge April 1, 2026 13:49
@maxime-oe maxime-oe added this pull request to the merge queue Apr 1, 2026
Merged via the queue into main with commit 3a2fe8e Apr 1, 2026
655 of 657 checks passed
@maxime-oe maxime-oe deleted the release/895.0.0 branch April 1, 2026 14:01
micaelae pushed a commit that referenced this pull request Apr 7, 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?
-->

## 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]
> **Medium Risk**
> Mostly release bookkeeping (version bumps, dependency bumps, lockfile
updates), but it propagates `@metamask/assets-controller@4.0.0` and
`@metamask/transaction-controller@64.0.0` which include breaking changes
that consumers must be compatible with.
> 
> **Overview**
> Bumps the monorepo version to `895.0.0` and rolls forward multiple
workspace package versions, updating their `CHANGELOG.md` entries
accordingly.
> 
> Updates inter-package dependencies to newer releases (notably
`@metamask/transaction-controller` to `64.0.0`,
`@metamask/assets-controller` to `4.0.0`, and related controller
packages), and refreshes `yarn.lock` to match.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fc4377c. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
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