Repository navigation
Conversation
tauri build produced no .sig updater artifacts because bundle.createUpdaterArtifacts was never set in tauri.conf.json — the release pipeline then aborted with 'No platforms assembled'. Signing keys were already wired via TAURI_SIGNING_PRIVATE_KEY secrets.
fix(release): enable createUpdaterArtifacts for updater signatures
🔍 Cora AI Code ReviewReview powered by cora-code · BYOK · MIT |
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
1 participant
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
Fast-follow to the v0.4.0 release prep: enables
bundle.createUpdaterArtifactsso the release build produces signed updater artifacts (.sig) for the auto-update manifest.Why
The v0.4.0 tag build produced no updater signatures and the manifest job aborted.
How
Config-only change in tauri.conf.json.
Testing