Same pattern as #235 did for 1.0.34, and for the same reason: the version bumps
for a shipped release were sitting uncommitted in the working tree, so master
would have kept declaring the previous version.
That is the exact drift #235 fixed a day earlier. It is worth committing
promptly rather than at the next release, because while it sits uncommitted the
repo is the only place anyone can look to answer "what is shipped?" and it gives
the wrong answer.
- app.json: 1.0.34 -> 1.0.35, versionCode 1000034 -> 1000035, buildNumber 37 -> 38
- ios project: MARKETING_VERSION 1.0.34 -> 1.0.35, CURRENT_PROJECT_VERSION 37 -> 38
- electron: 1.0.34 -> 1.0.35
- seeder-launcher (Start9 + Umbrel): 1.0.34 -> 1.0.35, with the matching pinned
image digest
Also records the release itself: the 1.0.35 App Store notes and the
metadata/ios/version/1.0.35/ archive, continuing the 1.0.17 to 1.0.34 pattern.
Deliberately NOT included: assets/app-ui.bundle and assets/bare-ios.bundle. Both
still predate the fixes merged for this release, so committing them would bake a
pre-fix artifact into the repo. They must be regenerated at build time.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPBW7sZJPAjkVRiqnB722W
Your NameandClaude Opus 4.8
940e3fdeb7