]>
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` | |
10 | 1. Push the changes `git push` | |
11 | 1. Push the new tag `git push --tags` | |
12 | 1. Get the hash of the file `sha256sum bip39-standalone.html` | |
13 | 1. Create the text for the release notes (see prior releases) | |
14 | 1. Sign the release notes `gpg --clearsign /tmp/releasenotes.txt` | |
15 | 1. Create a release on github from the tagged commit | |
16 | 1. include the signed release notes as text for the release | |
17 | 1. attach the bip39-standalone.html file | |
18 | 1. Add a new post to twitter from @bip39tool with the version, link and hash | |
8335cf17 | 19 | 1. Publish to any hosted locations (eg iancoleman.github.io/bip39) |