[v0.35.0] Sync master with release - #890
Conversation
Release candidate v0.35.0-rc.1
fix: upgrade wallet lib to v3.1.1 (#868)
… Home) (#878) The fee-token send refactor replaced the ModalPin/ModalSendTx flow with ModalTransactionOverview and ModalSendSuccess, dropping two behaviors: - The PIN field was no longer auto-focused. The overview modal relied on the input's `autoFocus`, which fires while the modal is still display:none, so the browser ignores it. Focus the field on Bootstrap's `shown.bs.modal` event instead (the old ModalPin approach), which also restores focus across every flow that uses the shared overview modal. - The success modal's "Close" (and top-right "x") only reset the form and stayed on the Send screen. They now navigate to the wallet home (/wallet/), restoring the pre-refactor behavior; the now-dead resetForm helper is removed.
… PIN) (#881) Fixes a batch of UX regressions introduced in the 0.35.0 release candidates: - Address mode kept across passphrase changes: adding/removing a passphrase no longer forces the wallet into multi-address mode. startWallet re-syncs the feature toggles from the live Unleash singleton before reading the single-address flag, so the clean_data reset in the passphrase flow no longer makes the flag read a stale default. - Import Tokens banner no longer advertises phantom tokens: unregistering a token with no history and zero balance now clears it from allTokens and tokensBalance, so fetchUnknownTokens stops reporting a token the import modal cannot resolve. - Easy Import Tokens "Open in Explorer" opens the system default browser via helpers.openExternalURL instead of a new Electron window. - Send Tokens confirmation validates the PIN with wallet.checkPin before sending, showing "Invalid PIN" on the review screen instead of a generic "Transaction failed" after a failed send attempt.
Release v0.35.0
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Superseded by #891. This branch ( |
2 participants
Acceptance Criteria
masterbranch with the changes from the latest releasev0.35.0Security Checklist