[OGPoyraz]

Explanation

Release 1367.0.0 with a major version bump for:

• @metamask/transaction-pay-middleware 1.0.0 → 2.0.0

@metamask/transaction-pay-middleware@2.0.0

Breaking: wallet_pay now selects the requested account before adding the transaction, once the request has passed every check (#11109)

• The messenger must now allow AccountsController:getAccountByAddress, AccountsController:getSelectedAccount and AccountTreeController:setSelectedAccountGroupByAccountId.
• A request whose from is not a known account is rejected with 4100.

Other changes:

• Add support for Node.js 26 (#10981)
• Accept a zero amount for perpsWithdraw, which opens the confirmation without a prefilled amount; adds optional allowZeroAmount to WalletPayFlow (#11114)
• Add dependencies @metamask/accounts-controller (^40.1.0) and @metamask/account-tree-controller (^11.2.0) (#11109)
• Bump @metamask/perps-controller from ^21.0.0 to ^22.0.0 (#11029)
• Bump @metamask/utils from ^12.0.0 to ^12.0.1 (#11107)

Dependency updates

No packages in the monorepo depend on @metamask/transaction-pay-middleware, so there are no downstream range updates. All upstream dependencies are already at their released versions and were marked intentionally-skip.

References

• #11109 — select the requested account for wallet_pay
• #11114 — accept a zero amount for perpsWithdraw

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]

✅ No changelog changes needed.

[github-actions]

This pull request has been closed

This release PR was automatically closed because it had no activity for 3 hours (last updated 3.1h ago).

Open release PRs are expected to merge promptly so they do not block others from starting a new release.

To keep a release PR open longer in exceptional cases, add the release:keep-open label.