From 11e9fd448223c4bb71959de32cde4a552eca9f5e Mon Sep 17 00:00:00 2001 From: Matej Kriz Date: Fri, 7 Jun 2024 13:04:27 +0200 Subject: [PATCH] chore(suite-desktop): delete totally outdated doc (cherry picked from commit 7c72badb69507dcfd3e428a568acf9f87a8759a0) --- docs/releases/desktop_updates.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/releases/desktop_updates.md b/docs/releases/desktop_updates.md index 56c709171d7..e1f932f68f1 100644 --- a/docs/releases/desktop_updates.md +++ b/docs/releases/desktop_updates.md @@ -7,12 +7,3 @@ The desktop build of Trezor Suite uses an auto-updating feature to keep the appl The package `electron-updater` (part of `electron-builder`) is used to manage updates. Information about updates is displayed in our UI and the user can perform actions related to them (trigger update, skip, etc...). In addition of what `electron-updater` provides us, we check signatures of downloaded files. For this to work, all files uploaded on Github need to have a signature attached with them. The signature will be checked against the SL signing key which is included in the application at build time. The key is located in `packages/suite-desktop-core/build/app-key.asc` and should be updated if the private key is changed. - -## How to publish an update - -1. Set the `GH_TOKEN` environment variable to a personal access token with access on the project repo scope. See [Github documentation](https://docs.github.com/en/free-pro-team@latest/github/authenticating-to-github/creating-a-personal-access-token) for more information. -1. Check the version you want to publish is correct. -1. Build all or a platform specific desktop build using `yarn workspace @trezor/suite-desktop run build:desktop` (all) or `yarn workspace @trezor/suite-desktop run build:linux` (platform specific/linux). -1. Publish all builds or a platform specific build using `yarn workspace @trezor/suite-desktop run publish:all` (all) or `yarn workspace @trezor/suite-desktop run publish:linux` (platform specific/linux). -1. Go to the Github Releases page, you should see a drafted release. -1. Update the content (which will be displayed in app as a change log) and publish the release.