]>
Commit | Line | Data |
---|---|---|
d2fea262 IC |
1 | Once all code changes for this version have been committed, a release can be |
2 | created with the following steps: | |
3 | ||
8335cf17 | 4 | 1. Run tests and ensure all tests pass |
d2fea262 IC |
5 | 1. Set the version in index.html |
6 | 1. Update changelog | |
7 | 1. Run `python compile.py` | |
8 | 1. Commit these changes with message `Release vX.Y.Z` | |
9 | 1. Tag the commit `git tag X.Y.Z` | |
d2fea262 IC |
10 | 1. Get the hash of the file `sha256sum bip39-standalone.html` |
11 | 1. Create the text for the release notes (see prior releases) | |
3d548c6f IC |
12 | 1. Sign the release notes `gpg --clearsign /tmp/signature.txt` |
13 | 1. Push the changes `git push` | |
14 | 1. Push the new tag `git push --tags` | |
d2fea262 IC |
15 | 1. Create a release on github from the tagged commit |
16 | 1. include the signed release notes as text for the release | |
3d548c6f IC |
17 | 1. include the changelog for this release as text for the release |
18 | 1. attach signature.txt.asc | |
d2fea262 IC |
19 | 1. attach the bip39-standalone.html file |
20 | 1. Add a new post to twitter from @bip39tool with the version, link and hash | |
8335cf17 | 21 | 1. Publish to any hosted locations (eg iancoleman.github.io/bip39) |
3d548c6f IC |
22 | 1. Download the file from the release and confirm it hashes to the expected value `sha256sum bip39-standalone.html` |
23 | 1. Download the signature from the release and verify it. `gpg --verify signature.txt.asc` |