chore(release): prepare VaultSync 2.0.1 build 37#139
Conversation
Version bump only: app + widget to 2.0.1/37 in ios/project.yml, and the CHANGELOG [Unreleased] section renamed to [2.0.1] — 2026-07-22. The only shipped change since 2.0.0 is the device-identity fail-closed fix (#135, merged as #138), which lives in go/bridge and therefore requires an xcframework rebuild before the archive — rebuilt and verified during this prep. What could go wrong and why this is safe: a skewed widget version or a missing CHANGELOG section would fail version-check.yml on the v2.0.1 tag; both were verified locally with the workflow's own checks (2x 2.0.1, single build number 37, section present). Full verification on this tree: Go bridge suite green (real Syncthing instances), gofmt clean, xcframework rebuilt from the patched tree, full Xcode plan 431/431 passed with zero failures/skips (xcresulttool-verified), strings key parity (884 keys) and design-token lint green. No StoreKit, entitlement, bundle-ID, or signing values were touched.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (4)
🧰 Additional context used📓 Path-based instructions (1)**/*⚙️ CodeRabbit configuration file
Files:
🔇 Additional comments (1)
📝 WalkthroughWalkthroughThe changelog now records version 2.0.1 dated 2026-07-22. The iOS app and widget use version 2.0.1 and build 37, while several indirect Go modules were updated. ChangesRelease updates
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 7✅ Passed checks (7 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The merge-blocking govulncheck gate on PR #139 flagged GO-2026-5970 (infinite loop on invalid input in x/text's Unicode normalization, fixed in 0.39.0): the bridge reaches norm.Form via StartSyncthing -> suture.Supervisor.ServeBackground and syncthing.EnsureDir. x/sys 0.46.0 and x/tools 0.47.0 move along as transitive requirements of the bump. What could go wrong and why this is safe: x/text is an indirect, API-stable dependency of the embedded Syncthing; no code changes were needed. Verified with the pinned scanner and the full suites on this tree: govulncheck v1.6.0 reports 0 called vulnerabilities, Go bridge suite green (real Syncthing instances), gofmt clean, xcframework rebuilt, and the full Xcode plan re-run against that framework: 431/431 passed, 0 failed, 0 skipped (xcresulttool-verified). The CHANGELOG 2.0.1 section gains the Security entry; no StoreKit, entitlement, bundle-ID, or signing values were touched.
Version bump to 2.0.1 (build 37, app + widget) and the CHANGELOG section for the #135 identity fail-closed fix (#138) — the only shipped change since 2.0.0. go/bridge changed, so the archive needs a fresh xcframework (rebuilt and verified during prep). Verification on this tree: Go bridge suite green, gofmt clean, full Xcode plan 431/431 zero fail/skip (xcresulttool-verified), strings parity 884 keys, design-token lint green, version-check logic mirrored locally.
Summary
CFBundleShortVersionString/CFBundleVersionaccordingly) and updated the release changelog.golang.org/x/textto 0.39.0 (fixes GO-2026-5970 infinite-loop DoS in Unicode normalization) with transitive moves tox/sys0.46.0 andx/tools0.47.0, and included a freshly rebuilt/verified Go bridge xcframework due togo/bridgechanges.Verification
govulncheck(pinned) reported zero called vulnerabilities.Security addendum (2026-07-22): the merge-blocking govulncheck gate flagged GO-2026-5970 (infinite loop on invalid input in
golang.org/x/text, reached by the embedded engine vianorm.Form). Fixed in the second commit by bumping x/text to 0.39.0 (x/sys 0.46.0 / x/tools 0.47.0 move along transitively) with a CHANGELOG Security entry. Re-verified on the bumped tree: pinned govulncheck v1.6.0 reports 0 called vulnerabilities, Go suite green, gofmt clean, xcframework rebuilt, full Xcode plan re-run 431/431 zero fail/skip (xcresulttool-verified).