Skip to content

Conversation

@Kriys94
Copy link
Contributor

@Kriys94 Kriys94 commented Nov 17, 2025

Explanation

Improve traces for BackendWebsocket and improve codease

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, highlighting breaking changes as necessary
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

Note

Publishes @metamask/core-backend@4.1.0 with improved WebSocket tracing/reconnection and updates assets-controllers to core-backend^4.1.0, along with monorepo/version and lockfile bumps.

  • Backend (packages/core-backend)
    • Release 4.1.0 with:
      • Improved WebSocket lifecycle tracing in BackendWebSocketService
      • Updated default reconnection backoff (reconnectDelay 10s, maxReconnectDelay 60s)
      • Simplified disconnection handling; add manual disconnect constants
      • Tooling: typescript v5.3, @ts-bridge/cli bump; fix missing dep in build script
  • Assets Controllers (packages/assets-controllers)
    • Bump @metamask/core-backend dev/peer deps to ^4.1.0
    • Changelog notes RPC fallback/timeouts (context)
  • Repo
    • Bump root version to 681.0.0
    • Update yarn.lock to reflect dependency changes

Written by Cursor Bugbot for commit fc4a74f. This will update automatically on new commits. Configure here.

@Kriys94 Kriys94 marked this pull request as ready for review November 17, 2025 11:52
@Kriys94 Kriys94 requested review from a team as code owners November 17, 2025 11:52
@Kriys94 Kriys94 merged commit 0720b9f into main Nov 17, 2025
272 checks passed
@Kriys94 Kriys94 deleted the release/681.0.0 branch November 17, 2025 12:01
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.

3 participants