Guard release version + document macOS first-launch trust#6
Merged
Conversation
Two small changes that together prevent the version-mismatch and first-launch-failure issues encountered with v0.1.1. release.yml: a 5-second sanity-check step now runs at the start of every matrix build and compares the tag (e.g. v0.1.2) against the version fields in tauri.conf.json, package.json, and Cargo.toml. Any mismatch fails the workflow immediately with a printed checklist of files to bump, instead of after a 15-minute build that emits binaries with the wrong version baked in (which is what happened with v0.1.1 → 0.1.0 filenames). READMEs: a short "First launch on macOS" section walks the user through the "Apple could not verify…" prompt that every new install hits because we ship ad-hoc-signed rather than notarized builds (notarization needs a paid Apple Developer ID). The instructions are deliberately brief — three steps, no rationale dump, no xattr workarounds. Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>
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.
Summary
Two small post-mortem fixes from the v0.1.1 release:
1.
release.yml: tag-vs-version sanity checktauri.conf.json/package.json/Cargo.toml, so every binary in the draft release was namedEchoWise_0.1.0_*despite the tag beingv0.1.1. This also breaks the in-app updater because the installed app self-reports the wrong version.v0.1.2) against the three version fields. Any mismatch fails the workflow immediately with a printed remediation checklist, so we don't pay for a 15-minute cross-platform build only to discover the artifacts are wrong.2. READMEs: macOS first-launch instructions
README.mdandREADME.zh.mdwalking them through System Settings → Privacy & Security → Open Anyway. Deliberately brief — no rationale dump, noxattrhacks.Test plan
v0.1.1vs0.1.0in tauri.conf.json would print::error::tauri.conf.json is '0.1.0' but the tag is 'v0.1.1'.and exit 1v0.1.2when ready) will exercise the check end-to-end🤖 Generated with Claude Code