chore(extension): 0.9.1 -> 0.9.2 (funding shown before approval) - #222
Merged
Conversation
Ships #221. Browsers only pick up an update when the manifest version increases. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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
1 participant
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.
Ships #221 — the batch approval window now shows what the funding address holds against what the run needs, and flags any chain that cannot cover its share.
Bumped in all three places:
package.json,manifest.chrome.json,manifest.firefox.json.Build verified from this commit —
dist/manifest.jsonreads 0.9.2, and both shipped fixes are confirmed present in the built bundles: thepage-acktransport fix from 0.9.1 and the "Paying from" funding panel from #221. 290 tests pass.🤖 Generated with Claude Code