Skip to content

1295.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 Sep 13:28
v1295.0.0
42a97bb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@metamask/chomp-api-service 6.0.0

Added

  • Add ChompIntentType export, covering every vault and subscription CHOMP intent type (#10430)
  • Add optional vedaPremiumProtocol service-details support alongside the required base vedaProtocol (#10430)

Changed

  • BREAKING: Widen the intent metadata type union (used by SendIntentParams, intent responses, and the service-details intentTypes struct) to include cash-deposit-premium, cash-withdrawal-premium, and cash-subscription, alongside the existing cash-deposit and cash-withdrawal (#10430)
  • Bump @metamask/utils from ^11.12.0 to ^12.0.0 (#10192)
  • Bump @tanstack/query-core from ^5.62.16 to ^5.89.0 (#9324)
  • Bump @metamask/base-data-service from ^2.0.0 to ^2.1.0 (#10502)

Fixed

  • Always fetch getIntentsByAddress fresh, so a follow-up read does not reuse a stale intent list and try to create intents that already exist (#10430)

@metamask/money-account-upgrade-controller 5.1.0

Added

  • Create the premium vault (pvmUSD) deposit and withdrawal delegations and register their CHOMP intents (cash-deposit-premium / cash-withdrawal-premium) when the moneyAccountPremiumVaultConfig flag is served for the base vault's chain and CHOMP's service details include vedaPremiumProtocol for that chain (#10430)
    • Add optional premiumVault to UpgradeConfig.
    • Resolve the premium delegation redeemer from CHOMP's vedaPremiumProtocol.adapterAddress; the remote feature flag only supplies vault contracts. A premium vault config served without a matching vedaPremiumProtocol in the service details response is dropped for that bootstrap run — the base vault still arms — and re-fetched on each later feature-flag or keyring trigger until CHOMP serves vedaPremiumProtocol for the chain. The base vault stays armed while re-fetching, including when a re-fetch fails or is skipped.
    • Accounts already upgraded re-run the upgrade once when the premium vault config is first served; only the premium pair is signed and registered.
    • Add VaultDelegationType type.
  • Add forceUpgradeAccount(address) method and MoneyAccountUpgradeController:forceUpgradeAccount messenger action, which skips the recorded-upgrade shortcut and always runs the upgrade steps so the base and, when configured, premium vault delegations and CHOMP intents exist before an action that depends on them (#10430)
    • Each step still only acts when its own remote check finds it not already done, so a call that finds everything in place signs and writes nothing.

Changed

  • Bump @metamask/utils from ^11.12.0 to ^12.0.0 (#10192)
  • Bump @metamask/authenticated-user-storage from ^4.0.0 to ^4.1.0 (#10400)
  • Bump @metamask/keyring-controller from ^28.0.0 to ^28.1.0 (#10418)
  • Bump @metamask/chomp-api-service from ^5.0.0 to ^6.0.0 (#10430)
  • Bump @metamask/money-account-utils from ^2.0.0 to ^2.1.0 (#10423, #10430, #10505)

@metamask/money-account-utils 2.1.0

Added

  • Add MONEY_ACCOUNT_PREMIUM_VAULT_CONFIG_FLAG_NAME and getMoneyAccountPremiumVaultConfig for the moneyAccountPremiumVaultConfig remote feature flag (#10430)
    • The premium flag is parsed with the same MoneyAccountVaultConfig shape as moneyAccountVaultConfig; its Veda adapter comes from CHOMP service details.

Changed

  • Bump @metamask/transaction-controller from ^72.0.0 to ^72.0.1 (#10462)
  • Bump @ethersproject/abstract-provider from ^5.7.0 to ^5.8.0 (#10477)
Assets 2
Loading