Skip to content

chore(release): prepare VaultSync 2.0.2 build 38 - #166

Merged
psimaker merged 1 commit into
mainfrom
chore/release-2.0.2
Aug 27, 2026
Merged

chore(release): prepare VaultSync 2.0.2 build 38#166
psimaker merged 1 commit into
mainfrom
chore/release-2.0.2

Conversation

@psimaker

@psimaker psimaker commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • set the app and widget to VaultSync 2.0.2 build 38
  • close the changelog section with the confirmed release-preparation date
  • leave signing, entitlements, bundle IDs, product IDs, and runtime behavior unchanged

Verification

  • xcodegen generation passed
  • generated app and widget plists both report 2.0.2 build 38
  • version, date, repository, privacy, localization, and release-metadata guards passed
  • independent release review found no remaining issue

Not verified

  • exact-Candidate XCFramework rebuild and complete Candidate test campaign begin only after this release commit is
    merged

Summary

  • Prepare VaultSync 2.0.2 build 38.
  • Update the app and widget versions from 2.0.1 (37) to 2.0.2 (38).
  • Close the changelog with the confirmed date, 2026-08-27.
  • Document fixes for sync reliability, folder access persistence, conflict handling, background-sync reporting, and malformed saved device IDs.
  • Include the Go runtime security update.
  • Keep signing, entitlements, bundle IDs, product IDs, privacy behavior, and runtime behavior unchanged.

Verification

  • Passed xcodegen generation.
  • Passed app and widget plist version checks.
  • Passed version, date, repository, privacy, localization, and release-metadata guards.
  • The exact Candidate XCFramework rebuild and complete Candidate test campaign remain pending until the release commit is merged.

Set the app and widget to version 2.0.2 build 38 and close the release changelog with the confirmed
preparation date.

What could go wrong and why this is safe: mismatched target versions or an incorrect changelog section can block
release validation or produce an inconsistent archive. Both generated target plists were verified as 2.0.2/38, while
signing, entitlements, bundle IDs, product IDs, and runtime behavior remain unchanged.

Not verified: the exact merged Candidate still requires a fresh Go 1.26.6 XCFramework build and the complete
isolated release-candidate test campaign.
@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9c0de711-a809-4185-85c6-e984a03a7eb0

📥 Commits

Reviewing files that changed from the base of the PR and between 55c94c6 and 8774f54.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • ios/project.yml

Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review.

📜 Recent review details
🧰 Additional context used
📓 Path-based instructions (3)
This generates the Xcode project and Info.plist. Review changes for bundle ID,

⚙️ CodeRabbit configuration file

Files:

  • ios/project.yml
Review public documentation for technical accuracy, privacy/security claims, App Store-facing wording,

⚙️ CodeRabbit configuration file

Files:

  • CHANGELOG.md
VaultSync syncs private Obsidian notes through Syncthing. Treat data loss,

⚙️ CodeRabbit configuration file

Files:

  • ios/project.yml
  • CHANGELOG.md
🔇 Additional comments (2)
ios/project.yml (1)

67-68: LGTM!

Also applies to: 141-142

CHANGELOG.md (1)

7-7: LGTM!


📝 Walkthrough

Walkthrough

The PR records the 2.0.2 release date and updates the VaultSync app and widget marketing versions and build numbers.

Changes

Release metadata

Layer / File(s) Summary
Release and version updates
CHANGELOG.md, ios/project.yml
The changelog records version 2.0.2 dated 2026-08-27. The VaultSync app and widget versions change to 2.0.2 with build 38.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to 8774f

This change only updates the app and widget release version/build metadata and closes the changelog entry; no actionable merge-blocking risk remains after normal checks and review.

Poem

Version numbers neatly align
A dated release enters the line
App and widget build
Their new numbers yield
Two-oh-two, ready to shine

🚥 Pre-merge checks | ✅ 7
✅ Passed checks (7 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title uses conventional-commit style and accurately describes preparation of the VaultSync 2.0.2 build 38 release.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
No Private Note Leakage ✅ Passed The pull request changes only CHANGELOG.md and ios/project.yml. The added lines update the release heading and app/widget version values from 2.0.1 (37) to 2.0.2 (38). No logging, analytics, diagnosti…
Bounded Ios Background Work ✅ Passed PASS: The release commit changes only CHANGELOG.md and ios/project.yml. It changes version metadata and release text. The diff contains no Swift, Objective-C, or background-execution API changes. …
Bridge Contract Compatibility ✅ Passed The pull request changes only CHANGELOG.md and version fields in ios/project.yml. The exact diff contains no Go bridge or Swift bridge-service source, declaration, JSON shape, or test changes. The…
Full details: No Private Note Leakage

Explanation

The pull request changes only CHANGELOG.md and ios/project.yml. The added lines update the release heading and app/widget version values from 2.0.1 (37) to 2.0.2 (38). No logging, analytics, diagnostics, crash reporting, or network-request code changed, so the check's explicit leakage condition is not introduced.

Full details: Bounded Ios Background Work

Explanation

PASS: The release commit changes only CHANGELOG.md and ios/project.yml. It changes version metadata and release text. The diff contains no Swift, Objective-C, or background-execution API changes. Therefore, this custom check is not applicable, and the commit introduces no stated background-work failure condition.

Full details: Bridge Contract Compatibility

Explanation

The pull request changes only CHANGELOG.md and version fields in ios/project.yml. The exact diff contains no Go bridge or Swift bridge-service source, declaration, JSON shape, or test changes. Therefore it does not introduce a documented Swift-Go bridge contract break.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-2.0.2

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@psimaker

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@psimaker
psimaker merged commit eb83ade into main Aug 27, 2026
19 checks passed
@psimaker
psimaker deleted the chore/release-2.0.2 branch August 27, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant