Skip to content

Port upstream 0.55.0: refresh spend on provider updates - #381

Merged
Finesssee merged 2 commits into
mainfrom
port/055-spend-invalidation
Aug 24, 2026
Merged

Port upstream 0.55.0: refresh spend on provider updates#381
Finesssee merged 2 commits into
mainfrom
port/055-spend-invalidation

Conversation

@Finesssee

Copy link
Copy Markdown
Collaborator

Summary

  • port upstream CodexBar v0.55.0 Usage & Spend publication/invalidation behavior from fix(spend): silent refresh and invalidation coverage steipete/CodexBar#3106
  • silently refresh the open Usage & Spend pane when provider snapshots publish updates
  • debounce provider-update bursts so one multi-provider refresh does not trigger one dashboard rebuild per event
  • strengthen the backend summary cache revision with limit/balance/currency and exact daily spend points

Upstream evidence

Validation

  • cargo test --manifest-path apps/desktop-tauri/src-tauri/Cargo.toml usage_spend --no-fail-fast -> compile/test pass
  • focused rustfmt and git diff --check -> pass
  • frontend Vitest remains blocked locally by the existing pnpm/Corepack shim failure; hosted CI/final frontend gate must exercise the listener path

Scope

Usage & Spend refresh/invalidation only. No provider-auth or version bump changes.

@Finesssee

Finesssee commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator Author

Thermo-nuclear re-review

Previous finding is closed: initial/manual and silent provider-update refreshes now share one summary-fetch function with explicit visible vs silent state behavior. TypeScript no-emit typecheck passes when using the repository-installed dependency tree.

Verdict: APPROVED.

@Finesssee
Finesssee force-pushed the port/055-spend-invalidation branch from be9dd3f to d533330 Compare August 24, 2026 20:59
@Finesssee
Finesssee merged commit d3912f5 into main Aug 24, 2026
1 check passed
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.

1 participant