Skip to content

619.0.0

Choose a tag to compare

@github-actions github-actions released this 14 Oct 18:20
932bbce

@metamask/assets-controllers 81.0.0

Changed

  • BREAKING: Bump peer dependency @metamask/core-backend from ^1.0.1 to ^2.0.0 (#6834)

Fixed

  • Fix address casing in WebSocket-based token balance updates to ensure consistency (#6819)

@metamask/bridge-controller 52.0.0

Changed

  • BREAKING: Bump peer dependency @metamask/assets-controllers from ^80.0.0 to ^81.0.0 (#6834)

@metamask/bridge-status-controller 51.0.0

Changed

  • BREAKING: Bump peer dependency @metamask/bridge-controller from ^51.0.0 to ^52.0.0 (#6834)

@metamask/core-backend 2.0.0

Added

  • BREAKING: Add required argument channelType to BackendWebSocketService.subscribe method (#6819)
    • Add channelType to argument of the BackendWebSocketService:subscribe messenger action
    • Add channelType to WebSocketSubscription type
  • BREAKING: Update Asset type definition: add required decimals field for proper token amount formatting (#6819)
  • Add optional traceFn parameter to BackendWebSocketService constructor for performance tracing integration (e.g., Sentry) (#6819)
    • Enables tracing of WebSocket operations including connect, disconnect methods
    • Trace function receives operation metadata and callback to wrap for performance monitoring
  • Add optional timestamp property to ServerNotificationMessage and SystemNoticationData types (#6819)
  • Add optional timestamp property to AccountActivityService:statusChanged event and corresponding event type (#6819)

Changed

  • BREAKING: Update BackendWebSocketService to automatically manage WebSocket connections based on wallet lock state (#6819)
    • KeyringController:lock and KeyringController:unlock are now required events in the BackendWebSocketService messenger
  • BREAKING: Update Transaction type definition: rename hash field to id for consistency with backend API (#6819)
  • BREAKING: Add peer dependency on @metamask/keyring-controller (^23.0.0) (#6819)
  • Update BackendWebSocketService to simplify reconnection logic: auto-reconnect on any unexpected disconnect (not just code 1000), stay disconnected when manually disconnecting via disconnect (#6819)
  • Improve error handling in BackendWebSocketService.connect() to properly rethrow errors to callers (#6819)
  • Update AccountActivityService to replace API-based chain support detection with system notification-driven chain tracking (#6819)
    • Instead of hardcoding a list of supported chains, assume that the backend has the list
    • When receiving a system notification, capture the backend-tracked status of each chain instead of assuming it is up or down
    • Flush all tracked chains as 'down' on disconnect/error (instead of using hardcoded list)
  • Update documentation in README.md to reflect new connection management model and chain tracking behavior (#6819)
    • Add "WebSocket Connection Management" section explaining connection requirements and behavior
    • Update sequence diagram to show system notification-driven chain status flow
    • Update key flow characteristics to reflect internal chain tracking mechanism

Removed

  • BREAKING: Remove getSupportedChains method from AccountActivityService (#6819)