GITmaxed Versioning & Release Policy — How Releases Track Upstream

GITmaxed versions follow GitHub Desktop. Each GITmaxed release is built on a stable upstream GitHub Desktop release, carries the fork's multi-account patches on top, and is published as a "GITmaxed Patch" release. This page explains the naming scheme, what you can expect from each release, and how release notes are organized.

Version naming scheme

Release titles follow the pattern:

GITmaxed Patch V<x.y.z>

The version number you see in the app equals the upstream GitHub Desktop version it tracks — for example, a fork release built on upstream stable x.y.z is titled "GITmaxed Patch V<x.y.z>". This makes parity easy to verify at a glance.

What a typical release contains

Category	Source	Description
Upstream changes	GitHub Desktop stable	All features, fixes, and dependency updates from the upstream release the version tracks
Multi-account layer	GITmaxed fork	Simultaneous accounts, per-repository assignment, folder-based auto-assignment, credential routing
Branding & packaging	GITmaxed fork	GITmaxed identity across UI, installer, and the Windows integration layer
Security maintenance	GITmaxed fork	Dependency pins and audit passes beyond what upstream ships, when needed
Updater feed	GITmaxed fork	New release title registered so the in-app updater can detect it

What changes vs. what never changes

• Changes with each release: bug fixes, upstream features, performance work, dependency updates.
• Never changes: multi-account behavior, your settings format, repository compatibility, shortcuts, the interface layout, and the MIT license.

Release notes structure

Each release announcement follows the same layout: (1) which upstream version is tracked, (2) upstream changes listed with their original context, (3) fork-specific notes (if any), (4) security/dependency notes, (5) upgrade instructions. Historical release notes are available on the project's releases page.

Support policy

• Only the latest published GITmaxed release is supported.
• Older GITmaxed releases keep working (nothing remotely disables them) but do not receive fixes.
• Issues should be reproduced on the latest release before reporting.

Tip: because the updater compares release titles exactly, a "new version" window appearing on every launch means your installed title doesn't match the published release name — reinstalling from the matching release resolves it. See the Updates page for details.

FAQ

Does GITmaxed lag behind GitHub Desktop?

GITmaxed releases follow upstream stable releases — each fork release ships as soon as the rebase and testing are complete. Beta upstream builds are not tracked; only stable.

Can I downgrade to an older GITmaxed release?

Yes — older builds remain downloadable. Settings and accounts carry across versions within the same major family; very old builds may need a one-time re-sign-in.

Where do upstream release notes come from?

From the official GitHub Desktop changelog — fork release notes credit upstream PRs rather than rewriting them.