Skip to content

Release/1115.0.0 - #9464

Merged
ccharly merged 3 commits into
mainfrom
release/1115.0.0
Jul 10, 2026
Merged

ccharly merged 3 commits into
mainfrom
release/1115.0.0

Conversation

@ccharly

@ccharly ccharly commented Jul 10, 2026 •

Copy link
Copy Markdown
Contributor

Explanation

Releasing the multichain-account-service to drop the old createAccount v1 flow from BIP-44 Snaps.

Also releasing the accounts-controller to re-align the @metamask/eth-snap-keyring major version in the clients dep tree.

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
Ships behavioral account-creation changes (v1 createAccount removal) and eth-snap-keyring major alignment via dependency bumps, though this PR only changes versions and lockfiles.

Overview
Monorepo release 1115.0.0 that cuts and wires new versions of @metamask/accounts-controller (39.0.5) and @metamask/multichain-account-service (12.1.0), then bumps those dependencies (and changelogs / yarn.lock) across the affected workspace packages.

multichain-account-service@12.1.0 (documented for this release) drops the legacy v1 createAccount path for BIP-44 Snaps in favor of createAccounts, to avoid side effects such as auto-selecting a non-EVM account after creation that conflict with the group model.

accounts-controller@39.0.5 is a patch release that realigns declared dependencies—notably @metamask/eth-snap-keyring ^23.0.0—so client dependency trees pick up the intended major version alongside related keyring/messenger bumps already noted in that package’s changelog.

No runtime source changes appear in this diff; it is version, changelog, package.json, and lockfile updates to publish the above.

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

@ccharly

ccharly commented Jul 10, 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 July 10, 2026 13:49
@ccharly
ccharly requested review from a team as code owners July 10, 2026 13:49
@ccharly
ccharly temporarily deployed to default-branch July 10, 2026 13:50 — with GitHub Actions Inactive
@ccharly
ccharly temporarily deployed to default-branch July 10, 2026 13:50 — with GitHub Actions Inactive
@metamask-ci

metamask-ci Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

✅ No changelog changes needed.

@ccharly
ccharly added this pull request to the merge queue Jul 10, 2026
Merged via the queue into main with commit e0d5853 Jul 10, 2026
425 checks passed
@ccharly
ccharly deleted the release/1115.0.0 branch July 10, 2026 13:57

### Removed

- Removed use of v1 `createAccount` entirely ([#9460](https://github.com/MetaMask/core/pull/9460))

@cryptodev-2s cryptodev-2s Jul 10, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should this be a breaking change ?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I talked to Charly and we will revert this release and re-create it.

@cursor cursor Bot mentioned this pull request Jul 10, 2026
4 tasks
@ccharly ccharly mentioned this pull request Jul 10, 2026
4 tasks

This branch was previously deployed

1 inactive deployment
default-branch — 8a3e6a09 Deployed Jul 10, 2026 by ccharly via Update changelogs #2067
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