Updating GITmaxed — How the Updater Works and How to Install New Versions

GITmaxed checks for updates automatically and offers new versions through a built-in updater window. This page explains how the update check works, what the updater window shows, and how to update manually.

Automatic update check

When GITmaxed starts (and periodically while running), the updater reads the installed release title and compares it with the latest published GitHub release for the project:

• Titles match exactly — you are current; the updater stays silent. No window, no interruption.
• A newer, differently named release exists — the updater opens a window showing the release name, version tag, release page link, and local publish time, with a button to open the releases page for download.
• GitHub unreachable (offline, API error) — the updater shows a clear error state instead of a stale version claim.

Why exact names matter: the updater compares release titles as literal strings. The installed title always looks like "GITmaxed Patch V…" — see the Versioning & Release Policy page for how release names are formed.

Updating manually

1. Open the project's releases page in a browser.
2. Download the latest GITmaxed release build.
3. Close GITmaxed completely.
4. Install the new version (installer) or extract the portable build over/next to the old one.
5. Start GITmaxed — settings, accounts, and repository assignments are preserved because they are stored outside the application folder.

What is preserved across updates

• All signed-in accounts and their tokens
• All repository entries and their account assignments
• Preferences (appearance, behavior, notifications)
• The repositories themselves and their entire Git history — updates never touch your clone folders

Troubleshooting the updater

• Update window shows every launch even though you are current: your installed title does not exactly match the published release name — install the build from the matching release.
• "Status: error" window: the updater could not reach the GitHub API — check internet connection, proxy, or firewall rules for api.github.com. The application remains fully usable without update checks.
• Old build starts after updating: close all GITmaxed processes and start again from the new install location.

FAQ

Does GITmaxed auto-download updates in the background?

No silent background downloads — the updater informs you and links the official release; you install when ready. The only "silent" path is when you are already current and the check simply does nothing.

Can I disable update checks?

Update checks contact the GitHub releases API only — they carry no repository data. If your environment blocks them, the app continues working and just cannot inform you of new versions.

Do I lose my accounts when updating?

No — accounts, tokens, and repository assignments live in per-user application data, not inside the program folder.