Updating Vegha

How Vegha updates depends on which build you installed.

Direct builds — Velopack auto-update

The Windows .exe and macOS .pkg direct downloads include Velopack auto-update:

1. In the background, Vegha checks the GitHub releases feed for a newer version.
2. If one exists, it downloads a delta package — only the bytes that changed, not the whole app.
3. The update is applied the next time you restart Vegha.

Updates are silent and incremental. You can also check manually from Help → Check for updates.

This background update check is the only automatic outbound request Vegha ever makes. It contacts the GitHub releases endpoint and nothing else — no analytics ride along. See Data & Privacy.

Store builds — store-managed

Microsoft Store (MSIX) and Mac App Store builds defer updates entirely to the store. The app contains no update-check code: the store decides when to deliver a new version, according to your OS update settings. Help → Check for updates is hidden in these builds.

Linux AppImage — manual

The Linux AppImage does not self-update. Download the latest Vegha-linux-x64.AppImage from the releases page and replace the old file. Settings and collections are untouched.

Release channels

Vegha publishes stable releases only. Each release on GitHub has:

• The platform installers (.exe, .pkg, .AppImage).
• Generated release notes describing what changed.
• Velopack feed files (RELEASES, *.nupkg) that power delta updates.

Your data is never touched by an update

Updates replace only the application binary. Your workspace folders, collections, environments, and settings live separately and survive every update — and every uninstall. Nothing about an update migrates or rewrites your .bru files.