chore: release v1.1041.0 - #12550
Merged
Merged
Conversation
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
#12540) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…sion (#12543) Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: asset-generation-bot <action@github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Flag check:
VITE_FEATURE_ROBINHOOD,VITE_FEATURE_NEAR_INTENTS_SWAP, andVITE_FEATURE_SWAPPER_RELAYare alltruein.envwith no.env.productionoverride, so every commit in this release is production-facing. The only flags OFF in prod areTHORCHAIN_TCY_ACTIVITY,AGENTIC_CHAT,FLOWEVM, andCELO, and no commit touches them.Production changes - testing required
Exact output swaps (NEAR Intents + Relay)
Adds a buy-amount-driven quoting mode: the user specifies exactly what they want to receive and the sell amount comes back derived from the route, with routing narrowed to NEAR Intents and Relay. Swappers that cannot support it return
ExactOutputNotSupportedinstead of silently falling back. Test both directions of amount entry (typing in the sell field and the buy field) on NEAR Intents and Relay, confirm the received amount matches what was requested, and confirm other swappers still quote normally from the sell side. In the widget, test the payment-mode props (defaultBuyAmountCryptoBaseUnit) and confirm a locked buy amount stays fixed while routes change.Robinhood chain in production
Turns on Robinhood Chain (EVM 4663) for all users; the underlying support shipped previously in #12497. Test wallet connection and account discovery on Robinhood across supported wallets (Native, Ledger, KeepKey, Trezor, Coinbase, Phantom, Vultisig, GridPlus, WalletConnect), send/receive of the native asset, and swaps in and out via Relay, Across, deBridge, ButterSwap, Bebop, and 0x.
Asset search and display fixes
Chain-native assets were being dropped from general search when another asset on the same chain shared a coingecko id (TON native vs the TON jetton), and fiat precision was wrong in the same area. Search for chain-native assets that have same-name tokens (TON especially), confirm they appear in general search and the asset selector, and spot-check that fiat values display with correct precision.
WalletConnect pairing
Wallets like Bridge Wallet rejected pairing with
UNSUPPORTED_CHAINSwhen their selected network was Ethereum, becauseeip155:1was advertised only as a required chain. Pair Bridge Wallet (and other WalletConnect wallets) while their active network is Ethereum, then repeat on a non-Ethereum network to confirm no regression.Fixes, deps, and infra
Routine asset data regeneration - no testing required.
Dev/local only - no production testing required
None. No commits in this release are behind a feature flag that is off in production.