Repository navigation
Automate desktop release builds and preparation - #4
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Desktop releases currently require manually updating the renderer submodule and package versions before starting a build. This adds a workflow that takes the approved Showcode commit, synchronizes the desktop version, and records a release commit and tag.
Installers are built for macOS, Windows, and Linux, then checked against their updater manifests before being uploaded to a draft release. Publishing remains a manual step after testing the downloaded installer. The new
npm run release:localcommand builds a local preview with production updates disabled.The release bot credentials are configured in both repositories. Merge this before the companion Showcode automation so the desktop workflow is available when release PRs start dispatching builds.
Validation: desktop tests, workflow linting, and a local macOS preview build with ad-hoc signature verification passed.