docs(adr): remote upgrade via GitHub — unified core+skin auto-update - #7
Closed
brettchien wants to merge 2 commits into
Closed
docs(adr): remote upgrade via GitHub — unified core+skin auto-update#7brettchien wants to merge 2 commits into
brettchien wants to merge 2 commits into
Conversation
Tauri updater checks a latest.json on GitHub Releases, downloads a signed per-platform bundle, verifies, installs — core+skin version together. Two signatures (updater vs OS code-signing) kept distinct; OS certs deferred (unsigned dev builds until then). Appendix carries the tauri.conf/release.yml pieces to drop in at console slice-2. Builds on ADR-3.
…m, term
- macOS arm64: builds are ad-hoc-signed (Tauri default), not 'unsigned'; a truly
unsigned app won't launch — first-run is a Gatekeeper gate, not a warning
- fix §5 app-stores parallelism ('... fit a control-plane tool poorly')
- normalize 'update signature' → 'updater signature'
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Closing as superseded by implementation: unified core+skin auto-update via GitHub is shipped — |
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.
ADR-4. Prep for shipping updates through GitHub, per the thread (option A: unified).
Decision: core+skin ship as one signed bundle per platform; the Tauri updater checks a
latest.jsonon GitHub Releases, downloads, verifies the update signature, installs. A tag push (vX.Y.Z) → CI builds macOS/Windows, signs, publishes.Two signatures kept distinct (§3.3): the updater signature (Tauri minisign keypair — required, cheap) vs OS code-signing (Apple notarization / Windows Authenticode — paid, deferred; unsigned dev builds until then).
Not committed yet: the
tauri.conf.jsonupdater block +release.ymllive in the appendix (§7) and drop in at console slice-2 (whensrc-tauriexists), so the pipeline is ready but nothing broken lands now.Open (need your call, §6): OS code-signing certs now vs unsigned first; public-repo release distribution OK?; updater private-key custody/rotation.
Draft — for review/wording pass.