release: 1.0.0 — iOS + Mac App Store launch prep#170
Merged
Conversation
Bump both platforms to 1.0.0 for the public App Store launch: - iOS MARKETING_VERSION 0.2.10 -> 1.0.0 (build 100000) - desktop 0.8.0 -> 1.0.0 (package.json, tauri.conf.json, Cargo.toml, Cargo.lock) Decision: ship 1.0 to BOTH the iOS App Store and the Mac App Store in parallel (ADR-004, supersedes ADR-003's MAS deferral). Direct-download DMG stays live. Docs: ADR-004, docs/app-store/launch-1.0-checklist.md (the actionable runbook), release-notes-v1.0.0.md, and an updated app-store README. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Opening a file in an app-owned (GitHub) vault could show a black screen: the reader loads a rendered `<doc>.html` sibling via WKWebView.loadFileURL (so relative images resolve), but the sibling is written just after first paint (.task) — so the first load hit a missing file, and any file:// read-access failure left the transparent web view over a dark background (= black). Make the app-owned render path self-healing, without losing relative-image fidelity: - ReaderView passes the in-memory `html` to the app-owned ReaderWebView as a baseline (the key still keys off the file URL, so reload behavior is unchanged). - ReaderWebView loads the on-disk file when it exists; otherwise it renders the in-memory HTML immediately (never blank), then upgrades to the file once the sibling is written (token bump). - A new didFailProvisionalNavigation degrades to the in-memory HTML if a file load fails (read-access/not-found), ignoring deliberate link-interception / external-open cancels. The HTML baseline is the same path folder vaults already render successfully, so the reader can no longer black-screen; loadFileURL still provides relative images when it succeeds. Co-Authored-By: Claude Opus 4.8 (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.
Prep for the 1.0 public launch on both the iOS App Store and the Mac App Store, in parallel.
Version bumps (→ 1.0.0)
MARKETING_VERSION0.2.10 → 1.0.0 (derived build 100000, > prior 2100)package.json,src-tauri/tauri.conf.json,Cargo.toml(+Cargo.lock)Decision
Ship 1.0 to both App Stores in parallel — ADR-004, which supersedes ADR-003 §3 (the "defer MAS to post-1.0" call). The signed + notarized direct-download DMG stays live alongside MAS.
Docs
docs/decisions/ADR-004-app-store-1.0.md— the decision recorddocs/app-store/launch-1.0-checklist.md— ⭐ the actionable runbook (iOS + MAS, account-gated steps marked)docs/release-notes-v1.0.0.md— release notes draft (used as the GitHub Release body at tag time)docs/app-store/README.mdNot in this PR (account-gated, tracked in the checklist)
MAS certs + provisioning + GitHub
MAS_*secrets; App Store Connect listings, screenshots, and "Submit for Review" for both. The iOS binary pipeline (EAS → ASC) and the MAS build (scripts/build-mas.sh+ CImasjob) are already in place.🤖 Generated with Claude Code