Revus 1.3.12-1 is a maintenance refresh of the opt-in public beta, with no new user-visible features. Stable remains at 1.3.10. This candidate is not a stable upgrade and has not completed the participant or live rollback acceptance for issue #185. Use disposable profiles and synthetic repositories, and follow the beta download page and field-test protocol before testing. macOS package validation remains deferred until v2.0.

Revus 1.3.11-1 is an opt-in public beta for Windows x64 and Linux x64. Stable remains at 1.3.10; this candidate is not a stable upgrade and has not yet completed the participant or live rollback acceptance for issue #185. Start from the beta download page, use disposable profiles and synthetic repositories, and review the field-test protocol before sharing results. macOS package validation is deferred until v2.0.

Revus API 0.3.1 adds an automatic retention sweep for raw anonymous telemetry. Events are removed once their server-side creation time is more than three calendar months old. This retention period applies to API event records; it does not define hosting-provider or reverse-proxy log retention.

Revus 1.3.10 lays the groundwork for safer update-channel recovery. The rollback procedure still needs a later eligible release and a real field rehearsal before the public-beta rollback acceptance can be considered complete. Restoring a channel does not downgrade an already-updated installation.

Revus 1.3.9 narrows the information that can leave the app in a support diagnostics export. The public-beta test protocol is ready for real Windows and Linux participants, but beta validation and rollback remain open work rather than completed claims.

Revus 1.3.8 makes the public-beta boundary explicit. The release includes a repeatable readiness check and an acceptance matrix covering upgrades, rollback, recovery, migration, diagnostics redaction, offline collaboration, and platform limitations without rushing the product to 2.0.

Revus 1.3.7 hardens the local telemetry privacy boundary. Events still capture safe product diagnostics, while sensitive property names and values such as credentials, URLs, and filesystem paths are discarded before they can be queued.

Revus 1.3.6 makes cross-platform readiness easier to understand. Diagnostics now identifies the current platform, distinguishes the installed desktop runtime from a browser preview, and explains which dialog, shell, editor, updater, and credential-helper behaviors are available.

Revus 1.3.5 adds crash-safe recovery continuity for interrupted Git operations. After a restart, Diagnostics can show the last detected operation and conflict count without collecting repository contents, credentials, or raw paths in an exported support bundle.

Revus 1.3.4 improves accessibility in the critical interaction surfaces used to act, navigate, and decide about optional telemetry. Keyboard focus stays inside open dialogs, returns to the launching control afterward, and primary navigation now exposes its current destination to assistive technology.

Revus 1.3.3 adds the operational guidance needed to support recovery-ready releases. The new playbook explains how to collect safe diagnostics, handle platform and credential-helper differences, recover interrupted Git operations, and verify signed upgrades or protected channel rollbacks.

Revus 1.3.2 adds safer recovery readiness for the early release. Preferences and shortcuts can be transferred through a versioned file, while diagnostics can be exported as a redacted support bundle without repository contents, provider secrets, or unbounded local history.

Revus 1.3.1 adds a focused review inbox for provider collaboration. Pull-request checks, reviews, comments, and required actions can now be triaged from one provider-neutral surface, with clear refresh, stale-state, and partial-failure feedback while keeping the existing provider boundaries intact.

Revus 1.2.0 adds a provider collaboration foundation directly to the desktop workspace. Authenticated repository workflows now show the capabilities and permissions available for the selected provider, so review work can begin with clear context about what the connection can do.

Revus 1.0.2 keeps repository work inside the product. Every value and confirmation now uses the same focused modal system, so tags, branches, remotes, reviews, and recovery actions feel like parts of one deliberate workspace.

Revus 1.0.1 makes advanced Git actions easier to find and harder to misapply. Branches and commits now carry the actions that change them, tags are visible where branches live, and an interrupted operation announces itself instead of hiding in a separate workflow panel.

Revus 1.0.0 completes the dependable daily-use path for local Git work. History and recovery are visible, native tools are integrated with clear boundaries, and long-running operations provide enough context to retry or recover safely.

Revus 0.9.0 brings the core Git workflows into one visual desktop workspace. You can now move from repository setup through tags, integration, conflict recovery, and patch exchange while keeping the repository state visible at each step.

Revus 0.8.0 makes remote work predictable without interrupting local Git workflows. Fetches are performed before relevant branch operations and can run automatically in the background, with clear safeguards for dirty worktrees, active operations, hidden windows, and unavailable remotes.

Revus 0.7.1 hardens the provider review workflow and verifies the native desktop path against the release binary. Provider failure states remain visible, and native review flows now surface clearer support and recovery guidance.

Revus 0.7.0 brings repository actions and provider-aware review work closer to the place where changes are made. Pull requests, checks, comments, and merge actions now have a clearer home in the desktop workflow, with provider differences kept visible and credentials kept local.

Revus 0.6.0 hardens the native workflow around settings, diagnostics, credential helpers, and safe local development preferences while expanding Linux desktop smoke coverage.

Revus 0.5.2 hardens the everyday change-review surface and makes long-running repository work easier to follow.

Revus 0.5.1 makes updates easier to control while keeping privacy and artifact verification explicit.

Revus 0.5.0 adds a native Git stash workflow for preserving work while moving between branches.

Revus 0.4.1 adds transparent, opt-in product tracking while keeping the application fully functional without consent.

Revus 0.4.0 makes application updates easier to understand and keeps the final restart in the user’s hands.

Revus 0.3.1 refines the remote workflow by keeping remote configuration and operations available without taking space from the primary workspace navigation.

Revus 0.3.0 adds the first complete remote-workflow surface: inspect configured remotes, run remote Git operations, follow their progress, and recover from common failures with actionable guidance.

Revus 0.2.1 brings the visual identity and desktop presentation together with a new logo, custom window frame, and refreshed application chrome.

Revus 0.2.0 focused on making repository navigation, history, and everyday Git workflows clearer and more dependable.

This is a website and project-foundation entry, not a desktop application release. The product roadmap and build availability will be updated as Revus develops.