-
Notifications
You must be signed in to change notification settings - Fork 244
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Electron Bug Fixes and Miscellaneous Changes (#2441)
* migrate the downloadpage generation script to this repo * tiny docs fix * fix 2 electron issues * support intel platform * fix save preferences bug
- Loading branch information
Showing
18 changed files
with
6,194 additions
and
60 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,41 +1,55 @@ | ||
# Release Guide | ||
|
||
## Creating release notes | ||
|
||
### Pre-requisites | ||
|
||
- You need the correct upstream master. You should see | ||
```bash | ||
git remote -v | grep upstream | ||
|
||
```bash | ||
git remote -v | grep upstream | ||
upstream [email protected]:cryptoadvance/specter-desktop.git (fetch) | ||
upstream [email protected]:cryptoadvance/specter-desktop.git (push) | ||
``` | ||
|
||
- You need a GitHub token: | ||
If you don't have one, get one here https://github.com/settings/tokens and make sure to tick the boxes for repo and workflow as below: | ||
If you don't have one, get one here https://github.com/settings/tokens and make sure to tick the boxes for repo and workflow as below: | ||
|
||
![](./images/release-guide/github-token.png) | ||
|
||
Using the new token, run | ||
```bash | ||
export GH_TOKEN=YOURTOKEN | ||
``` | ||
|
||
```bash | ||
export GH_TOKEN=YOURTOKEN | ||
``` | ||
|
||
- You need Docker running | ||
- Checkout the master branch and ensure a clean workspace. | ||
|
||
Now, you can run | ||
|
||
```bash | ||
./utils/release.sh --release-notes | ||
``` | ||
|
||
Or, if you want to directly set the new version: | ||
|
||
```bash | ||
./utils/release.sh --new-version v1.13.1 --release-notes | ||
``` | ||
|
||
## Creating a new tag | ||
|
||
Update your master branch after the release notes PR ([example](https://github.com/cryptoadvance/specter-desktop/commit/65ff6959d7fd85cba745e4d454b30031839f857f/)) has been merged and then run: | ||
|
||
```bash | ||
git tag v1.13.1 && git push upstream v1.13.1 | ||
``` | ||
|
||
## GitLab - releasing stage | ||
Creating a tag triggers the release process of the GitLab runners. | ||
There exists a mirror of the GitHub repo on GitLab, but only when a tag is created on GitHub will the release part of the runners execute. You can check the status here: | ||
|
||
Creating a tag triggers the release process of the GitLab runners. | ||
There exists a mirror of the GitHub repo on GitLab, but only when a tag is created on GitHub will the release part of the runners execute. You can check the status here: | ||
https://gitlab.com/cryptoadvance/specter-desktop/-/pipelines | ||
|
||
There are three stages: | ||
|
@@ -50,14 +64,17 @@ The first relevant stage is "releasing". Here, the Windows, Linux and pip releas | |
- specter_desktop-v1.13.1-x86_64-linux-gnu.tar.gz | ||
|
||
The three jobs in more detail: | ||
|
||
- release_binary_windows: is creating a binary for specterd and for Windows (Windows runner) | ||
- release_electron_linux_windows: Creates a specterd for Linux, an AppImage for Linux and an executable for Windows (Linux runner). | ||
- release_pip: Is releasing a pypi package on [pypi](https://pypi.org/project/cryptoadvance.specter/) and creates a tarball of the pip package for the GitHub release page (Linux runner). | ||
- release_pip: Is releasing a pypi package on [pypi](https://pypi.org/project/cryptoadvance.specter/) and creates a tarball of the pip package for the GitHub release page (Linux runner). | ||
|
||
For details look at `.gitlab-ci.yml` | ||
|
||
## MacOS | ||
|
||
Ideally, directly after the tag is created, start with the MacOS release. This has to be done manually, for now. There is a script for this: | ||
|
||
```bash | ||
./utils/build-osx.sh --version v1.13.1 --appleid "Satoshi Nakamoto (appleid)" --mail "[email protected]" make-hash specterd electron sign upload | ||
``` | ||
|
@@ -70,54 +87,37 @@ This script also runs `github.py upload `, so two more binares and the hash and | |
- SHA256SUMS-macos.asc | ||
|
||
## GitLab - post releasing | ||
Back to GitLab, the final stage is "post releasing". | ||
|
||
Back to GitLab, the final stage is "post releasing". | ||
|
||
In this stage, the invididual SHA256-hashes and signatures are combined into two final files: | ||
|
||
- SHA256SUMS | ||
- SHA256SUMS.asc | ||
|
||
Everything, apart from the MacOS files, are pulled from the GitLab environment, the MacOS files from GitHub. | ||
Don't forget to delete the two MacOS files (`SHA256SUMS-macos` and `SHA256SUMS-macos.asc`) on the GitHub release page in the end. | ||
|
||
## Trouble shooting | ||
|
||
If the MacOS signatures are missing, it can happen that the following Exception will be raised: | ||
|
||
```bash | ||
File "/builds/cryptoadvance/specter-desktop/utils/github.py", line 295, in download_artifact | ||
raise Exception( | ||
Exception: Status-cod04 for url ... ) | ||
``` | ||
|
||
In any case, if the macOS binaries arrive on GitHub too late, you have to manually delete the already created `SHA256SUMS` and `SHA256SUMS.asc`, otherwise the upload to GitHub will fail if you rerun the release signatures job on GitLab - for details see ([this PR](https://github.com/cryptoadvance/specter-desktop/pull/689)). The green arrow in the screenshot is where you rerun the release signatures job on GitLab: | ||
|
||
![](./images/release-guide/rerun-release-signatures.png) | ||
|
||
## Editing the text on the GitHub release page | ||
We are running a script here to create a markdown file that can be used for copy and paste. The script uses the latest release on GitHub to create links to the artifacts in the release, so it only makes sense to run it once the previous step has been completed. | ||
- Checkout this repo: `[email protected]:cryptoadvance/corp-notes.git` | ||
- `cd download-page` | ||
- Run `./build.sh` | ||
|
||
The result `gh_page.md` can be found in the build directory. | ||
Edit the release on GitHub and paste the md-file there along with the release notes from `release-notes.md`. | ||
|
||
## Website | ||
The above script also produces html files for the website (in the same directory). The second item needs to have the release notes on GitHub, otherwise the content for the details button is missing. So, you need to re-run `./build.sh` after the release notes on GitHub are done. | ||
- `download-page_current.html` | ||
- `download-page_releases.html` | ||
|
||
Login into: https://specter.solutions/wp-login.php | ||
|
||
- Go to "Pages" | ||
- Hover over "Specter Desktop - Elementor" and choose `Edit with Elementor` | ||
- Click somewhere on area 1 (see screenshot), then somewhere on area 2, select all, delete, and paste: `download-page_current.html` | ||
|
||
![](./images/release-guide/website-1.png)\ | ||
- Then click `update` | ||
Note: If you see jinja tags, you probably pasted some templates. | ||
|
||
Do the same for the "Specter Releases" part, just, in this case, replace with:\ | ||
`download-page_releases.html` | ||
|
||
![](./images/release-guide/website-2.png)\ | ||
## GitHub release page and download page | ||
|
||
You can then just exit the editing with Elementor. | ||
This is handled by the script `./utils/generate_downloadpage.sh`. As a prerequisite, you need to clone the `specter-static` repo which contains the specter website. Clone it on the same level than specter-desktop. | ||
Running that script will: | ||
|
||
- install the prerequisites (basically markdown, see pyproject.toml) | ||
- generate the GH-page and the download-page based on the `utils/templates`. | ||
- Asks whether it should replace/update/initialize the Github Release page for the latest version | ||
- copies over the new download-pages and asks whether it should commit/push those |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.