Getting started · Update

Update RepoOps

RepoOps keeps itself current so a tracked-repo change reaches the running dashboard without a manual git pull + restart. Auto-update is on by default; the in-app banner tells you when a new version is staged.

Overview

There are two update layers. Desktop auto-update (the installed Electron shell) ships new application versions from the in-app feed and prompts to install on quit. Source-mode auto-update (the self-updating aggregator) keeps the dashboard server itself current with the latest released code - it polls every 15 minutes, fast-forwards main, and quietly relaunches.

Where to find it

  • Banner at the top of the dashboard window when an update is staged.
  • Settings App updates for the toggle + manual "Check now".
  • ⌘ K > sync for the verb to fetch the mirror for the active repo.

How auto-update works

  1. Polls every 15 minutes

    In source mode the server fetches the git remote every 15 minutes and compares your checkout to the upstream sha. The Settings tab reads that status from /api/update/status. The installed desktop app updates separately through electron-updater against the RepoOps update feed at repoops.ai/updates/. When a new sha is available and the working tree is fast-forwardable, the update is applied automatically. 0 downtime - the supervisor relaunches with the new code and the dashboard reconnects.

  2. Shows a banner when applying

    The dashboard window shows Updating… reconnecting while the relaunch is in flight. ~5 seconds.

  3. Falls back to a manual prompt when it can't FF

    If your working tree has local changes (source mode) or the auto-merge isn't safe, the banner switches to Update available · Apply & restart. Click when you're ready.

Configure

  • Toggle from Settings. Settings App updates has the on/off switch. Default: on.
  • Env var hard-off. Set REPOOPS_AUTO_UPDATE=0 in your environment to force auto-update off everywhere. The banner still shows when an update is available; it just won't self-apply.
  • Choose a channel. Currently only the main channel ships. Beta/canary channels arrive with signed builds.

Force an update right now

  1. Open Settings.
  2. App updates Check now.
  3. If one's available, the banner appears with Apply & restart. Click it.
  4. Wait ~5 seconds for the relaunch. The dashboard reloads in place.

When an update is blocked

⚠
“Working tree isn't fast-forwardable.”
You have uncommitted local changes in the source-mode checkout. Either commit them, stash them, or open the terminal and git stash before clicking Apply.
⚠
Apply fails after click
Open %APPDATA%\repo-dashboard\server.log (Windows) and look for theupdater lines. The most common cause is a git auth issue against the remote.

Why auto-update is on by default

We ship roughly weekly. New tabs land, bugs get fixed, security guardrail rules sharpen. An out-of-date install gets out-of-sync with the brain conventions in your repos and the badges start lying. The default is on so your dashboard stays useful without you thinking about it.

Roll back to the previous version

In the desktop app, Settings App updates shows Roll back to v<version>, and the tray menu shows the same item, when the update server lists an older version. The app never goes back on its own. After you click, it checks that the older version can read this device's database and asks you to confirm in its own dialog. It then downloads that version, restarts and installs it. Your data directory is kept.

Updates then pause, so the version you left does not come back by itself. A version published after it still installs as usual. To take the newer version again, click Resume updates in the same section.

⚠
When the button is disabled
Hover it for the reason. The common ones: the update server lists no older version that supports rollback (versions published before rollback existed cannot be rolled back to), the server could not be reached, or the older version cannot read the database this version wrote. In the last case, stay on this version, or copy the data directory (%APPDATA%\repo-dashboard on Windows, ~/.repo-dashboard elsewhere) somewhere safe before installing the older version by hand.

An older version that finds data a newer version changed in ways it cannot read stops at launch and names the version to install, instead of opening the database. That check exists in versions from this release on.

Source mode keeps the previous git ref reachable; run git checkout HEAD~1 in the checkout if a release breaks something.

Last updated