Skip to content

chore: promote staging to production - #329

Open
github-actions[bot] wants to merge 8 commits into
mainfrom
staging
Open

chore: promote staging to production#329
github-actions[bot] wants to merge 8 commits into
mainfrom
staging

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown

Changes


Auto-generated — merge when staging is validated.

* feat: improve epoch and date formatting across explorer

* feat: add comment about rail rate change impact on settlement calculation

* refactor: extract EpochTimeCell to reduce ternaries

* refactor: replace epoch display with timestamp in funded until column

* feat: add debt display and improve funded until calculation in console

* fix: add explicit BigInt conversion

* chore: address copilot review comments

* refactor: replace epoch-based timing with timestamp-based calculations

* feat: convert payment rates from per-epoch to per-day

* refactor: display /day payment-rate in settleRailDialog

* refactor: improve funded until calculation and rail state labels

* refactor: improve settlement validation and add paused rail settlement logic

* refactor: centralize settlement eligibility logic

* refactor: rename settlementEpoch to currentEpoch and extract untilEpoch calculation

* chore: address review comment
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
filecoin-pay-explorer Ready Ready Preview Aug 23, 2026 11:54am

Request Review

* feat(console): add dedicated shell layout

Move the console pages into a (console) route group whose layout owns ConsoleProviders, the console header, and the wallet-connection gating, so pages no longer repeat that setup. URLs are unchanged.

Suppress the global site navigation on /console* via ConditionalNavigation. The footer still renders on console pages.

Keep notifications/verify outside the route group: it is an email link target and must render for a disconnected user. It shares ConsoleHeader, which stays free of wagmi so it can render without providers.

* fix: verify page footer
Add a console sidebar with Dashboard, Email Alerts, and Pay Explorer items. It renders inside the access gate, so a disconnected wallet still gets the connect state at full width with no sidebar.

Below `lg` the sidebar moves into a right-side sheet opened from a hamburger in the console header. The trigger's `lg:hidden` and the desktop column's hidden `lg:flex` are exact complements, so no viewport shows both or neither. The header now flips from stacked to inline at `md` rather than `sm`, and keeps the trigger on the logo row on narrow tablets.

The drawer closes on sidebar clicks and on any pathname change. Back and forward leave this layout mounted and fire no click to react to, so the click handler alone would strand the drawer over the destination page.

The Email Alerts item carries the notification status that `FundsSection` showed as a chip.  An unknown status renders a neutral bell with no ON/OFF label.
* feat: replace funds table with overview cards

The funds table repeated the same four figures per token row and called the funded-until derivation three times per row. A 4-up card grid now shows Balance, Locked, Available and Funded until for one selected token, defaulting to USDFC by contract address, with Deposit and Withdraw promoted to section actions.

Health tiers mirror the notification service thresholds of 30, 7 and 3 days, so the console and the alert emails agree on when an account is at risk. Expired funding shows the outstanding debt as a negative on the Available card.

Also widens the console token request past the default page of ten, so a zero-balance USDFC cannot sort off the end and mis-default the selector, and moves the alerts banner below the overview it reacts to.

* fix: snapshot dialog tokens when dialogs open

Deposit and Withdraw ran against the live selection, so a resolving query or a token switch could swap the target under a part-filled form. Each dialog now captures its token on open and keeps it until reopened, since clearing it would unmount the dialog mid-receipt.

Adds characterization tests for calculateFundedUntil, which had none.
* feat: add token picker to the deposit dialog

A single picker now shows the selected token and expands to the account's other tokens, with the custom-address path behind an "Add supported token" row. This restores adding a new token type, which the funds overview change removed with the table.

The dialog seeds its selection from the caller's snapshot and owns it afterwards, so switching tokens inside the dialog stays safe.

Caps the dialog at 90vh and bounds the token list, since DialogContent sets no max height and a centred fixed element that outgrows the viewport puts its title and footer out of reach.

* fix: mobile display of funds overview title

* fix(explorer): guard deposit flow during permit signing

Prevent duplicate submissions and dialog closing while a permit signature is pending.

Also restore token name validation, improve address status accessibility, and safely truncate token metadata.
* feat(explorer): add runway and locked balance meters to console

Add two visual meters below the funds overview to show account runway and the proportion of the balance that is locked.

Runway is measured against a 90-day horizon and uses the existing health tiers, keeping the 30, 7, and 3-day thresholds visually distinct. Longer runways cap at a full bar, with the duration label showing the actual remaining time.

Share the health tier colors between the overview and runway meter, allow metric values to wrap instead of truncate, and omit the year from dates when it matches the current year.

* fix: console layout ui

* fix(explorer): fix date and hour formatting boundaries

Update `formatFutureTimestamp` to switch units at the correct boundaries.

Timestamps of one day or more now display as dates, while one hour or more uses hours instead of only minutes.

Add tests covering these boundaries and the surrounding formatting behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants