Skip to content

Commit 6a98bee

Browse files
committed
docs: document release process
1 parent b14909d commit 6a98bee

2 files changed

Lines changed: 33 additions & 1 deletion

File tree

docs/release.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# Releasing Devtools
2+
3+
> This is for maintainers only.
4+
5+
## Pre-requisites
6+
7+
1. Make sure you have publishing rights to the `@vue/devtools` and `@vue/devtools-api` npm packages (check with `npm owner ls @vue/devtools`). If not, ping @yyx990803 for publishing permission.
8+
9+
2. Sign up and create [API keys for Firefox Addons](https://addons.mozilla.org/developers/addon/api/key/). Create `.amo.env.json` in project root with the keys:
10+
11+
```json
12+
{
13+
"apiKey": "...",
14+
"apiSecret": "..."
15+
}
16+
```
17+
18+
3. Run `npm run release:beta`.
19+
20+
If it completes without error, it should have published the necessary npm packages.
21+
22+
In addition, this should create the following files:
23+
24+
- `dist/chrome.zip`
25+
26+
This is the packed chrome extension which should be uploaded via [Chrome Web Store developer dashboard](https://chrome.google.com/webstore/devconsole). Note the items are under the `vuejs-dev` publisher group. We current have two extensions, one for beta (currently Vue 3 only) and one for stable (Vue 2 only). We will eventually replace the stable with this branch once it supports both Vue 2 and Vue 3, but for now the Vue 3 supporting version should be published under the beta channel.
27+
28+
- `distvue.js_devtools-x.x.x.zip`
29+
30+
Similarly, the stable version of the Firefox Addon can be updated [here](https://addons.mozilla.org/en-US/developers/addon/vue-js-devtools/edit). But before then, we simply publish it as a pre-signed zip file. It should be added as a binary to the GitHub release.
31+
32+
4. The release should have updated the versions of a few `package.json` files. Add and commit them, then add a git tag in the format of `v6.x.x`. Push both the commit and the tag to GitHub, and publish the release on GitHub (we should probably automate this with local script + GitHub actions).

sign-firefox.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ if (!fs.existsSync(credFile)) {
99
apiKey: '',
1010
apiSecret: ''
1111
}, null, 2), { encoding: 'utf8' })
12-
console.log('Please provide Mozilla API credentials in .amo.env.json\nhttps://addons.mozilla.org/fr/developers/addon/api/key/')
12+
console.log('Please provide Mozilla API credentials in .amo.env.json\nhttps://addons.mozilla.org/developers/addon/api/key/')
1313
process.exit(1)
1414
}
1515

0 commit comments

Comments
 (0)