chore(extension): version the store listing copy alongside the code - #198
Merged
Conversation
The tronbrowser.dev listing still advertised "Phase 1 ships wallet + receive; send and one-click x402 payment approval land in subsequent updates" — untrue since #189 shipped x402 approval and payBatch bulk payouts. The store's publish flow only refreshes the bundle, so the copy stayed frozen at whatever it said the day the listing was created. Keeping the text here means a publish can sync it from the repo that actually knows what shipped, via the store's new listing PATCH: LISTING=packages/extension/store-listing.json ./publish-extension.sh Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
There was a problem hiding this comment.
Pull request overview
Adds a version-controlled store listing payload for the CoinPay Wallet browser extension so the published listing copy can be kept in sync with what the extension actually ships.
Changes:
- Add
packages/extension/store-listing.jsoncontaining the extension’s store listing name/summary/description/homepage fields.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "name": "CoinPay Wallet", | ||
| "summary": "Non-custodial multi-chain wallet with one-click x402 payments and bulk payouts.", | ||
| "description": "CoinPay Wallet is a non-custodial, cross-browser (MV3) wallet for the CoinPay multi-chain platform.\n\n- Create or import a BIP-39 wallet. The seed is encrypted at rest (WebCrypto AES-256-GCM + PBKDF2) and never leaves your device; signing happens inside the extension's background worker, so private keys are never exposed to a web page.\n- Derives addresses for BTC, BCH, ETH, POL and SOL (with USDC on ETH/POL/SOL), matching the CoinPay web wallet.\n- Backup-confirmation gate before the wallet is usable, plus a configurable idle auto-lock.\n- One-click x402 (HTTP 402) payment approval for sites that request payment.\n- Bulk payouts: a site can request many payments at once via window.coinpay.payBatch and you approve the whole run once, with per-payment progress — built for payables queues like ugig.net's accepted-invoice list.\n- Sites connect per-origin and only after you approve the prompt.\n\nSource: https://github.com/profullstack/coinpayportal/tree/master/packages/extension", |
| @@ -0,0 +1,6 @@ | |||
| { | |||
v0.1.0 was cut today from a master that already contained #189 (bulk payments behind a single approval, x402 approval UI, the in-page provider and content bridge), so the released bundle carries those features under a version number that predates them. Chromium auto-update keys off the manifest version: with it pinned at 0.1.0 there is no upgrade signal, and anyone already on 0.1.0 stays there no matter what the store serves. Minor bump for a feature release, applied to package.json and both manifests so the Chrome and Firefox builds agree. 155 extension tests pass at 0.2.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
| { | ||
| "name": "@profullstack/coinpay-extension", | ||
| "version": "0.1.0", | ||
| "version": "0.2.0", |
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.
The tronbrowser.dev listing for CoinPay Wallet still advertises
Both shipped in #189. The bundle it serves is current — today's
extension-v0.1.0release — but the store's publish flow only refreshes the bundle, so the copy stayed frozen at whatever it said the day the listing was created (updated_atis still 2026-07-07).This adds
packages/extension/store-listing.jsonso the text lives in the repo that actually knows what shipped, and can be synced on publish:The
LISTINGstep and thePATCHendpoint it calls are in profullstack/tronbrowser.dev#43 — that needs to land first. Owners can also now edit the copy directly from the extension's page on the store.The description here is rewritten against what the extension actually does today: BIP-39 create/import with the seed encrypted at rest, signing confined to the background worker, BTC/BCH/ETH/POL/SOL (+USDC), backup gate and idle auto-lock, one-click x402 approval, and
payBatchbulk payouts behind a single approval.Follow-up not included here:
packages/extension/README.mdis stale the same way — it still says "Status — Phase 1 (wallet core) in progress".🤖 Generated with Claude Code