Revert "Release/628.0.0 (#6893)"

[micaelae]

This reverts commit b6301b3.

Explanation

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

Reverts the 628.0.0 release by downgrading versions, removing latest changelog sections, and aligning bridge-status-controller to @metamask/bridge-controller ^52.0.0.

• Release:
  • Downgrade root package.json version 628.0.0 → 627.0.0.
• Packages:
  • packages/bridge-controller:
    • Version 53.0.0 → 52.0.0.
    • Remove 53.0.0 changelog entry; update [Unreleased] compare link to start from 52.0.0.
  • packages/bridge-status-controller:
    • Version 51.0.1 → 51.0.0.
    • Remove 51.0.1 changelog entry; update [Unreleased] compare link to start from 51.0.0.
    • Downgrade @metamask/bridge-controller range in devDependencies and peerDependencies to ^52.0.0.
• Lockfile:
  • Update yarn.lock to reflect @metamask/bridge-controller@^52.0.0.

^{Written by Cursor Bugbot for commit 17aee70. This will update automatically on new commits. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​bridge-controller@​52.0.0

View full report

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		@metamask/[email protected] is a AI-detected potential code anomaly. Notes: The code appears to be a normal client-side bridge interaction layer for token data and quotes, with input normalization and validation and standard network I/O patterns. There is no evidence of malicious intent (no backdoors, no credential theft, no data exfiltration beyond expected API usage). The presence of streaming quotes and validation logging is typical for real-time financial quote systems. Overall risk is moderate due to external dependencies but not inherently malicious. Confidence: 0.72 Severity: 0.60 From: packages/bridge-status-controller/package.json → npm/@metamask/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[mcmire]

LGTM!