fix: refresh portfolio balances without hard reload#1187
Merged
w84april merged 3 commits intorelease/26-04-17from May 4, 2026
Merged
fix: refresh portfolio balances without hard reload#1187w84april merged 3 commits intorelease/26-04-17from
w84april merged 3 commits intorelease/26-04-17from
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
d4716fd to
37782f7
Compare
dd6ca47 to
00910b1
Compare
w84april
approved these changes
Apr 29, 2026
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.
Summary
Context
This splits the portfolio freshness work out from the Safe/Katana overlay branch.
The reported symptom was that portfolio holdings could stay stale across normal reloads or tab switches, while a hard refresh fixed the issue. That pointed to cached balance responses and insufficient foreground refetch behavior.
Test Plan