[abretonc7s]

Explanation

Releases @metamask/perps-controller 14.0.0 → 15.0.0. The monorepo version goes 1217.0.0 → 1218.0.0.

No other package is being published. Perps-controller has no in-monorepo dependents that need a workspace range bump.

The bump is major. Adding a new member to the public PerpsProviderType union is a breaking type change for exhaustive switches:

• Added (breaking): Lighter as a perps venue (initial implementation, disabled by default) (#9889, #10015). PerpsProviderType gains 'lighter'. Enablement requires client opt-in (providerCredentials.lighter.enabled, or the perpsLighterProviderEnabled remote feature flag plus a client-supplied providerCredentials.lighter.signerBridge). Without a bridge the provider is read-only. Lighter is off by default, so clients that do not opt in can upgrade without runtime behavior change; exhaustive PerpsProviderType switches still need a new case to typecheck.
• Fixed: Preserve accepted HyperLiquid Scale orders when part of a batch is rejected (#9989).

Changelog

Moved Unreleased entries in packages/perps-controller/CHANGELOG.md under [15.0.0]. Folded the pre-release Lighter validation follow-up (#10015) into the Lighter Added entry (as that PR intended). Breaking entry is prefixed with **BREAKING:** and includes adaptation notes.

References

• Source PRs: #9889, #10015, #9989

• No draft Mobile/Extension adoption PRs required to keep current clients compiling: Lighter stays disabled until clients opt in. Client work to enable Lighter (credentials, signer bridge, UI) is separate.

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

Made with Cursor

[metamask-ci]

✅ No changelog changes needed.