Repository navigation
Upgrade sdk@0.5.0-rc.24 and swap@0.1.0-rc.27 - #1087
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe pull request updates the ChangesDependency Version Update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
Deploying wallet-bitcoin with
|
| Latest commit: |
cd870f1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://894fe1f2.wallet-bitcoin.pages.dev |
| Branch Preview URL: | https://upgrade-sdk-0-5-0-rc24.wallet-bitcoin.pages.dev |
Deploying wallet-mutinynet with
|
| Latest commit: |
cd870f1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://acf031f9.arkade-wallet.pages.dev |
| Branch Preview URL: | https://upgrade-sdk-0-5-0-rc24.arkade-wallet.pages.dev |
arkana-ai-bot
left a comment
There was a problem hiding this comment.
Dependency bump: @arkade-os/sdk rc.23→rc.24, @arkade-os/swap rc.26→rc.27
Scope: package.json (4 lines changed) + pnpm-lock.yaml (generated, excluded from detailed review). No source changes.
What landed in rc.24 / rc.27
I cross-referenced the ts-sdk CHANGELOG.md (Unreleased section, commit 1f2456c) and the local clone at packages/{sdk,swap}. The two increments that matter for this wallet:
rc.27 (swap) — protocol-relevant fixes:
-
Dust-stuffed lockup fix (
@arkade-os/swap). Anyone paying dust to a lockup address previously causedpushClaim/pushRefundWithoutReceiverto take every output, exceedingmaxTxWeightand leaving funds permanently stuck. rc.27 caps lockup spends atMAX_LOCKUP_SPEND_INPUTS(16), largest-first, and the claim/refund manager re-runs on subsequent passes for any remainder. This is a real fund-recovery fix. -
Registry-outage / pinned card logic (
@arkade-os/swap). A registry outage previously replaced the cached markets with pinned cards only. Now only a live registry answer updates the cache; a registry-unreachable state surfaces assource: "local"onSnapshotRefand retries after one minute rather than sitting on the full TTL. This is theSnapshotRef.sourcebreaking-change entry in the changelog. -
Partial-refund mark fix.
arkadeRefunderno longer marks a partially-succeeded refund asfailed.
rc.24 (SDK): No individual RC changelog entry exists; the unreleased section covers the full 0.5.0 development line. The SDK bump tracks the swap package dependency update inside @arkade-os/swap.
Breaking-change audit against wallet source
The unreleased CHANGELOG lists several breaking changes. I searched src/ (excluding node_modules) for every affected symbol:
| Breaking change | Symbol(s) searched | Found in wallet src? |
|---|---|---|
receivePkScriptFor removed from @arkade-os/swap/protocol |
receivePkScriptFor |
No |
refundIfUnresolved / claimReceiveLockup / awaitLockupFunding / RefundOutcome removed from @arkade-os/swap/protocol |
all four | No |
RFQ_AD_KIND removed from @arkade-os/swap/nostr |
RFQ_AD_KIND |
No — wallet uses RFQ_DIRECTED_KIND (still exported) |
SnapshotRef.source gains "local" (exhaustive switch risk) |
SnapshotRef |
No switch on this field found |
IContractManager.dispose() returns Promise<void> |
IContractManager |
No direct usage in src/ |
ArkadeCashUnclaimedReason drops "swept" |
ArkadeCashUnclaimedReason, "swept" |
Not matched as a reason enum; wallet's "nothing-swept" is a different constant |
buildAndSubmitOffchainTx acquires wallet lock |
buildAndSubmitOffchainTx |
Not used in src/ |
All symbols the wallet actually imports from these packages (BTC_ASSET_ID, getAssetSwaps, findMarket, makeCachedFeedFetch, QUOTE_OPTIONS, validatePlan, lightningSendRequest, discoverMarkets, watchMarkets, RFQ_DIRECTED_KIND, nostrRfqTransport) remain exported in rc.24/rc.27 — confirmed against the ts-sdk source tree.
CI
All 7 checks green on cd870f1: Cloudflare Pages (mutinynet + bitcoin), unit tests, and E2E (core + assets-send, Chrome + Mobile Chrome).
Lockfile
Integrity hashes for both packages changed as expected. pnpm-lock.yaml shows @arkade-os/swap@0.1.0-rc.27 still resolves @arkade-os/sdk@0.5.0-rc.24 as its own dependency (consistent), and @arkade-os/solver-discovery pins remain at 0.3.0 (unchanged).
No issues found. The bump is safe to merge; rc.27 in particular closes a real fund-recovery risk.
Summary by CodeRabbit