Skip to content

Release/13.0.0 - #383

Merged
taran-a merged 3 commits into
mainfrom
release/13.0.0
Sep 29, 2026
Merged

taran-a merged 3 commits into
mainfrom
release/13.0.0

Conversation

@taran-a

@taran-a taran-a commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Explanation

Tron release changelog v4.0.0

Added

  • Add signProofOfOwnershipBatch for signing multiple proof-of-ownership messages in one request. (#265)
  • Emit Transaction Added, Transaction Approved, and Transaction Rejected for signTransaction confirmations (#333)
    • Only dApp-initiated transaction confirmations were affected; the unified send flow already emitted these events.
  • Report account synchronization failures to Sentry with the failing account IDs and their failure reasons (#374)

Changed

  • BREAKING Bump @metamask/keyring-api from ^23.7.0 to ^24.1.0 (#214)
  • BREAKING Bump @metamask/keyring-snap-sdk from ^9.2.1 to ^10.0.0 (#214)
  • BREAKING Bump @metamask/snaps-sdk from ^11.2.0 to ^12.0.1 (#214)

Removed

  • BREAKING Remove the deprecated asset cluster of handlers: onAssetHistoricalPrice, onAssetsConversion, onAssetsLookup and onAssetsMarketData (#263)

Fixed

  • Emit Transaction Submitted from the Wallet Standard signAndSendTransaction path so its transactions no longer reach Transaction Finalized without a matching submit event (#343)
  • Tolerate unknown fields in the Token API metadata response so that new fields added by the API no longer fail validation and fall back to default token metadata (#320)
Solana release changelog v7.0.0

Added

  • Add signProofOfOwnershipBatch for signing multiple proof-of-ownership messages in one request. (#256)
  • Add back the endowment:assets permission for the Solana scopes to the snap manifest, with no-op onAssetsLookup, onAssetsConversion, onAssetHistoricalPrice, and onAssetsMarketData entry points required to keep the permission (#274)
  • Report account synchronization failures to Sentry with the failing account IDs and their failure reasons (#376)

Changed

  • BREAKING: Bump @solana/kit from ^6.9.0 to ^8.3.0 and the @solana-program/* clients (compute-budget ^0.18.1, system ^0.14.1, token ^0.16.1, token-2022 ^0.17.0) to their Kit 8-compatible versions. (#303)
  • BREAKING: Update the Solana Name Service integration to SNS SDK v1 and the Kit 6.9-compatible Solana program clients (#271)
  • BREAKING Bump @metamask/keyring-api from ^23.7.0 to ^24.1.0 (#214)
  • BREAKING Bump @metamask/keyring-snap-sdk from ^9.2.1 to ^10.0.0 (#214)
  • BREAKING Bump @metamask/snaps-sdk from ^11.2.0 to ^12.0.1 (#214)
  • Reduce snap_getBip32Entropy calls in createAccounts from two to one for bip44:discover by deriving the activity-check address locally from the already-fetched coin-type node, and parallelize the entropy fetch with the existing-accounts state read for all creation paths (#304)
  • Coalesce concurrent AccountsSynchronizer.synchronize calls for the same account set so duplicate in-flight syncs (e.g. simultaneous connection-recovery events across mainnet and devnet) share one run instead of fanning out redundant asset and transaction fetches (#304)
  • Migrate trackError and withCatchAndThrowSnapError to @metamask/snap-networks-utils createSnapErrorHandling, and add getSnapProvider for Snap RPC access
  • Extract Snap-owned assets domain logic into SnapAssetsAdapter; AssetsService is a thin facade that delegates metadata, market data, fetch, persist, and account asset reads through the adapter (no Core routing yet). (#121)
  • Align AssetsService read API with snap-networks-utils / AssetsController shapes by adding getAccountAssetByID, getAccountAssetsByIDs, getAccountAssetsByScope, and getAccountAssets, and routing Keyring and Send through them (still Snap-owned storage). (#120)
  • Bump @metamask/utils from ^11.9.0 to ^11.11.9 (#161)

Removed

  • BREAKING Remove the onAssetsLookup, onAssetsConversion, onAssetHistoricalPrice, and onAssetsMarketData asset handler entry points, along with the now-unused handler modules and the endowment:assets permission (#261)
  • BREAKING Remove AssetsService.fetchAssetsMarketData and SnapAssetsAdapter.fetchAssetsMarketData, the TokenPricesService class, and PriceApiClient.getHistoricalPrices, all of which were only used by the removed asset handlers (#261)
  • Remove the now-unused PriceApiClient.getFiatExchangeRates method and related ExchangeRate type, the unused tokenPrices unencrypted state field, the unused fiatExchangeRates and historicalPrices price API cache TTL options, and unused price API test mocks (#261)

Fixed

  • BREAKING: Preserve dapp-origin signTransaction and signAndSendTransaction payloads by signing the decoded transaction directly (#156)
  • Prevent signing dapp transactions with expired blockhashes, and refresh the blockhash for MetaMask-originated transactions before signing. (#183)
  • Tolerate unknown fields in the Price API spot price and Token API metadata responses so that new fields
    added by the API no longer fail validation (#321)
  • Emit an AccountTransactionsUpdated keyring event with a pending unconfirmed transaction immediately after broadcasting.
Bitcoin release changelog v3.1.0

Added

  • Add signProofOfOwnershipBatch for signing multiple proof-of-ownership messages in one request. (#266)
  • Emit Transaction Added, Transaction Approved, and Transaction Rejected tracking events from Bitcoin transaction confirmations (#328, #329)
  • Report account synchronization failures to Sentry with the failing account IDs and their failure reasons (#375)

Fixed

  • Populate the from address of receive transactions by resolving the addresses that funded them through the chain indexer. Bitcoin inputs only reference a previous outpoint, so the sender was previously left empty. (#372)

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

@taran-a
taran-a requested review from a team as code owners September 29, 2026 13:07
@taran-a
taran-a deployed to default-branch September 29, 2026 13:07 — with GitHub Actions Active
@taran-a
taran-a deployed to default-branch September 29, 2026 13:07 — with GitHub Actions Active
@metamask-ci

metamask-ci Bot commented Sep 29, 2026

Copy link
Copy Markdown

✅ No changelog changes needed.

@taran-a
taran-a force-pushed the release/13.0.0 branch 2 times, most recently from fd2c189 to ec43f9d Compare September 29, 2026 13:34
@sonarqubecloud

Copy link
Copy Markdown

@taran-a

taran-a commented Sep 29, 2026

Copy link
Copy Markdown
Contributor Author

@metamaskbot publish-preview

@github-actions

Copy link
Copy Markdown
Contributor

Preview builds have been published. Learn how to use preview builds in other projects.

Expand for full list of packages and versions.
@metamask-previews/bitcoin-wallet-snap@3.1.0-preview-a0f97e6c
@metamask-previews/snap-networks-utils@1.0.0-preview-a0f97e6c
@metamask-previews/solana-wallet-snap@7.0.0-preview-a0f97e6c
@metamask-previews/stellar-wallet-snap@1.1.0-preview-a0f97e6c
@metamask-previews/tron-wallet-snap@4.0.0-preview-a0f97e6c

@Battambang Battambang left a comment

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.

good, thx

@taran-a
taran-a added this pull request to the merge queue Sep 29, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 29, 2026
@taran-a
taran-a added this pull request to the merge queue Sep 29, 2026
Merged via the queue into main with commit c2d57fb Sep 29, 2026
56 checks passed
@taran-a
taran-a deleted the release/13.0.0 branch September 29, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants