Skip to content

Commit 616a047

Browse files
authored
Update submit.mdx
1 parent 563bab3 commit 616a047

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/pages/framework/workflows/submit.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ import { Callout } from "nextra-theme-docs"
66

77
# Submit Your Extension
88

9-
The Plasmo Framework ships with a convenient GitHub action called [Browser Platform Publish](http://bpp.browser.market/) or BPP. This action will automatically publish your extension to all supported browser extension stores. It runs on a manual trigger by default, but changing its config can make it run on every push.
9+
The Plasmo Framework ships with a convenient GitHub action called [Browser Platform Publish](https://github.com/marketplace/actions/browser-platform-publisher/) or BPP. This action will automatically publish your extension to all supported browser extension stores. It runs on a manual trigger by default, but changing its config can make it run on every push.
1010

1111
To start publishing your Plasmo extension, set up a `keys.json` file with the following schema:
1212

1313
```json
1414
{
15-
"$schema": "https://raw.githubusercontent.com/PlasmoHQ/bpp/v2/keys.schema.json"
15+
"$schema": "https://raw.githubusercontent.com/PlasmoHQ/bpp/v3/keys.schema.json"
1616
}
1717
```
1818

@@ -29,7 +29,7 @@ The final key might look like this:
2929

3030
```json
3131
{
32-
"$schema": "https://raw.githubusercontent.com/plasmo-corp/bpp/v2/keys.schema.json",
32+
"$schema": "https://raw.githubusercontent.com/plasmo-corp/bpp/v3/keys.schema.json",
3333
"chrome": {
3434
"clientId": "123",
3535
"refreshToken": "789",

0 commit comments

Comments
 (0)