Port upstream 0.55.0: refresh spend on provider updates - #381
Merged
Conversation
Collaborator
Author
Thermo-nuclear re-reviewPrevious 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
force-pushed
the
port/055-spend-invalidation
branch
from
August 24, 2026 20:59
be9dd3f to
d533330
Compare
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
Upstream evidence
v0.55.06538ac345/ fix(spend): silent refresh and invalidation coverage steipete/CodexBar#3106Validation
cargo test --manifest-path apps/desktop-tauri/src-tauri/Cargo.toml usage_spend --no-fail-fast-> compile/test passgit diff --check-> passScope
Usage & Spend refresh/invalidation only. No provider-auth or version bump changes.