Update App Store link for VaultSync in README

[psimaker]

What & why

Component(s)

• go (bridge / Syncthing)
• ios (app / widget)
• notify (relay)
• docs / CI

Testing

• cd go && make patch && go test -tags noassets ./bridge
• cd notify && go test ./...
• iOS build / xcodebuild test
• Not applicable

Summary

• Updated both README App Store links to the regional listing for VaultSync for Obsidian.
• No changes affect sync behavior, privacy, security, or background execution.
• No code or tests changed. Verification was not required for this documentation-only update.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Team

Run ID: f08ffc89-04ca-4ad4-a313-c80f0b7a6bec

📥 Commits

Reviewing files that changed from the base of the PR and between eb83ade and 5e4c510.

📒 Files selected for processing (1)

• README.md

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

📜 Recent review details

⏰ Context from checks skipped due to timeout. (5)

• GitHub Check: govulncheck (go bridge)
• GitHub Check: M5/M6 Syncthing Transfer E2E
• GitHub Check: Go Tests
• GitHub Check: Helper Runtime Packaging
• GitHub Check: Notify Tests

⚠️ CI failures not shown inline (2)

GitHub Actions: PR Title / 0_PR Title.txt: Update App Store link for VaultSync in README

Conclusion: failure

View job details

##[group]Run amannn/action-semantic-pull-request@v6.1.1
 with:
   types: feat
fix
docs
chore
refactor
test
ci
perf
build
style
revert
   githubBaseUrl: https://api.github.com
 env:
   GITHUB_***REDACTED_SECRET_ASSIGNMENT***
 ##[endgroup]
 ##[error]No release type found in pull request title "Update App Store link for VaultSync in README". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

---

GitHub Actions: PR Title / PR Title: Update App Store link for VaultSync in README

Conclusion: failure

View job details

##[group]Run amannn/action-semantic-pull-request@v6.1.1
 with:
   types: feat
fix
docs
chore
refactor
test
ci
perf
build
style
revert
   githubBaseUrl: https://api.github.com
 env:
   GITHUB_***REDACTED_SECRET_ASSIGNMENT***
 ##[endgroup]
 ##[error]No release type found in pull request title "Update App Store link for VaultSync in README". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

🧰 Additional context used

📓 Path-based instructions (2)

Review public documentation for technical accuracy, privacy/security claims, App Store-facing wording, setup correctness, and consistency with the free app plus optional Cloud Relay subscription model.

⚙️ CodeRabbit configuration file

Files:

• README.md

VaultSync syncs private Obsidian notes through Syncthing.

⚙️ CodeRabbit configuration file

Files:

• README.md

🔇 Additional comments (2)

README.md (2)

10-10: LGTM!

---

56-56: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Remove the space from the App Store URL.

The Quick start link contains v vaultsync-for-obsidian. Use the same destination as the App Store badge so users can open the listing.

Proposed fix

-1. **Install** VaultSync from the [App Store](https://apps.apple.com/de/app/v vaultsync-for-obsidian/id6761845197).
+1. **Install** VaultSync from the [App Store](https://apps.apple.com/de/app/vaultsync-for-obsidian/id6761845197).

As per path instructions, **/*.md files require technical accuracy and setup correctness.

			> Likely an incorrect or invalid review comment.

Source: Path instructions

---

📝 Walkthrough

Walkthrough

The README's App Store badge and Quick start install link now use the regional VaultSync for Obsidian App Store URL.

Changes

App Store links

Layer / File(s)	Summary
Update README App Store links README.md	The download badge and Quick start install step use the updated App Store path and app name.

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

Merge Risk: 🟡 Moderate · up to 5e4c5

The README’s Quick start installation link may fail to open the VaultSync App Store listing, preventing users from installing the app through the documented setup path. Correct the URL before merging.

Poem

Two links now point the way
To VaultSync's store display
The badge shines bright
Quick start takes flight
README rests in tidy array

🚥 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 clearly and concisely describes the README App Store link update. It does not use a conventional-commit prefix, but the requirement states that this style applies when practical.
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	PASS. The pull request changes only two README.md App Store URLs. The diff contains no code, logging, analytics, diagnostics, crash reporting, or network request changes, and it does not include note …
Bounded Ios Background Work	✅ Passed	PASS. The pull request changes only two App Store URLs in README.md. The diff contains no Swift, iOS source, or project-file changes, so it introduces no Swift background execution behavior and cannot…
Bridge Contract Compatibility	✅ Passed	PASS: The pull request changes only two App Store URLs in README.md (HEAD^..HEAD). No Go bridge, Swift bridge-service, or bridge test files changed. Therefore the documented Swift–Go bridge contra…

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch psimaker-patch-1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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