Skip to content

Release/4.0.0 - #106

Merged
ulissesferreira merged 4 commits into
mainfrom
release/4.0.0
Aug 4, 2026
Merged

Release/4.0.0#106
ulissesferreira merged 4 commits into
mainfrom
release/4.0.0

Conversation

@ulissesferreira

@ulissesferreira ulissesferreira commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Explanation

@metamask/snap-networks-utils package release v1.0.0

First publish of shared utilities for MetaMask network snaps.

Added

  • Scaffold @metamask/snap-networks-utils (#79)
  • Shared AssetsProvider for reading account assets from Core AssetsController (#82)
  • Shared RemoteFeatureFlagsProvider for reading remote feature flags from Core RemoteFeatureFlagController (#99, #102, #104)
  • Logger utilities (logger, createPrefixedLogger, noOpLogger) (#79)

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

@metamask-ci

metamask-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown

✅ No changelog changes needed.

@ulissesferreira
ulissesferreira added this pull request to the merge queue Aug 4, 2026
Merged via the queue into main with commit dc68460 Aug 4, 2026
46 checks passed
@ulissesferreira
ulissesferreira deleted the release/4.0.0 branch August 4, 2026 13:30
jeremytsng pushed a commit that referenced this pull request Aug 5, 2026
## Explanation
This PR adds support for recognizing and mapping SEP-41 token transfers
(invokeHostFunction contract transfer(from,to,amount)) across
transaction decoding, simulation, and activity mapping so SEP-41 sends
can appear as structured “Send” activity instead of always “Unknown”.

<img width="557" height="570" alt="image"
src="https://github.com/user-attachments/assets/a0ea84d0-4f8b-4097-b674-415ca972fde2"
/>



<!--
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
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