Add native Windows and Linux releases - #2
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.
What changed
.exehelper paths through manifests, the packaged runtime, and the Tauri sidecarWhy
The previous desktop runtime was only release-validated on macOS. Its setup scripts required Bash, Windows helper executables were not resolved with
.exe, and contract compilation invoked an unbundledpython3process. Those gaps could produce an installer whose covenant compile or local-preflight workflow failed on a clean Windows machine.Local verification
npm run setup:silverc: both pinned compiler commits built from sourcenpm run setup:kascov-preflight: pinned Kascov preflight engine built from sourcenpm run verify: 37/37 tests passed, syntax checks passed, Vite production build passedcargo fmt --check: passed.apppassed strict deep code-signature verificationRelease boundary
The GitHub Release will be created only from the v0.2.1 tag after all native Runner jobs succeed. Windows packages are not Authenticode-signed, Linux packages are not distribution-signed, and macOS is ad-hoc signed without notarization.
SilverScript and the KCC721 pack remain experimental and TN10-first. KCC721 standalone and mainnet deployment remain blocked.