Release 1315.0.0

[abretonc7s]

Explanation

Releases @metamask/perps-controller 19.0.0 → 20.0.0. The monorepo version goes 1314.0.0 → 1315.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. Public unions and Lighter order validation change:

• BREAKING: Lighter placeOrder / validateOrder accept supported native attached TP/SL instead of refusing all attachments. Gate forwarding on attachedTpsl. (#10638)
• BREAKING: Grouped Lighter signer calls require grouping/count 1/2 or 2/2 with two orders, or 3/3 with three orders. (#10638)
• BREAKING: ScaleOrderChild.state adds canceled. (#10638)
• BREAKING: DirectProviderOrderCapabilitiesUnavailableReason and OrderCapabilitiesUnavailableReason add order_market_unsupported. (#10638)
• BREAKING: Stray triggerPrice on Lighter basic market/limit orders is refused with ORDER_TRIGGER_PRICE_NOT_SUPPORTED. (#10638)
• BREAKING: Lighter position TP/SL replacement and removal preserve independent partial triggers. (#10638)
• BREAKING: OrderFill.pnl is optional when the venue omits realized PnL. Treat missing as unknown, not zero. (#10605)

Also ships Lighter Scale/Chase/TWAP probe work, fee quote attribution (feeSource, metamaskFeeDiscountBips), HyperLiquid agent/signing fixes, quieter optional-messenger failures, and watchlist hydration/write races.

Changelog

Moved Unreleased entries in packages/perps-controller/CHANGELOG.md under [20.0.0]. Removed Uncategorized monorepo release markers (1311–1314) that do not affect package consumers. Dropped a duplicate Chase probe summary already covered by more specific entries.

References

• Source PRs: #10638, #10618, #10605, #10643, #10650, #10651, #10665, #10670, #10683
• No in-monorepo consumer packages to bump. Mobile and Extension exhaustive union matches need the new members on upgrade. Lighter attached TP/SL stays gated on attachedTpsl and client rollout.

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