chore(perps-controller): bump @nktkas/hyperliquid to ^0.33.3 - #10591
Merged
Merged
Conversation
- Drop the SDK yarn patch; 0.33.3 no longer ships amd-module directives - Remove the retired dexAbstraction migration (userSetAbstraction path) - Map new HyperLiquid order types and make liquidatedUser optional
…ze unified-account migration waiters
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
Author
|
@metamaskbot publish-previews |
Contributor
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
10 tasks
abretonc7s
enabled auto-merge
September 30, 2026 03:25
geositta
approved these changes
Sep 30, 2026
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Sep 30, 2026
## Explanation - Release major perps-controller 19.0.0 Breaking changes (see changelog): - `OrderFill.liquidation.liquidatedUser` is now optional - `FrontendOrder.orderType` union adds `Twap Slice`, `Vault Close`, `Spot Dust Conversion` - Removed `LighterPersonalSigner` and the `personalSigner` / `l1Address` fields of `LighterAuthConfig` ## References - #10414, #10437, #10464, #10559, #10588, #10589, #10591 ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
Bumps
@nktkas/hyperliquidfrom^0.33.1to^0.33.3in@metamask/perps-controller(v0.33.2, v0.33.3)./// <amd-module name="file:///home/runner/...">directives from the SDK's.d.tsfiles.0.33.3no longer ships them, so the patch and its rootresolutionsentry are gone. The builtdisthas nofile:///references.dexAbstractionmigration removed.0.33.2droppeddexAbstractionfromuserAbstraction/userSetAbstractionto match the API: HyperLiquid retired the mode (the liveuserAbstractionendpoint now returns"default"for the SDK's formerdexAbstractionfixture users). TheuserSetAbstractionmain-wallet migration and its "don't re-prompt after a rejection" cache were dead, so they are removed.default/disabledaccounts still migrate throughagentSetAbstraction, and deferral withallowUserSigning: falseis unchanged. An unexpecteddexAbstractionresponse now takes the existing unknown-mode bail.FrontendOrder.orderTypeaddsTwap Slice,Vault CloseandSpot Dust Conversion. They are mapped explicitly to'market'in historical orders, which is what the fallback already returned.OrderFill.liquidation.liquidatedUseris now optional (HyperLiquid omits it on some liquidation fills), and the re-exportedFrontendOrder.orderTypeunion gains the three values above. Mobile (PerpsFillTag) and Extension (perps-fill-tag) already guardliquidatedUserat runtime; their localtransactionHistorytypes declare it asstringand may need?when adopting this release.OrderProcessingStatusfrom the SDK now maps explicitly (exhaustivesatisfiesmap): the specific*Rejectedstatuses reportrejectedandoutcomeSettledCanceled/internalCancelreportcanceled, where they previously fell through toqueued.agentSetAbstractionconcurrently.References
18.0.1-preview-2848be6, device recipe evidence): chore(perps): adopt @metamask/perps-controller 19.0.0 (HyperLiquid SDK 0.33.3) metamask-mobile#37025Checklist