GitPerennial v1.1.0

GitPerennial v1.1.0 — Multiple GitHub accounts

Track repos across more than one GitHub account or organization from a
single GitPerennial install.

Downloads

Platform	File	Status
Windows	GitPerennial-v1.1.0.msi	✅ Available
macOS	GitPerennial-v1.1.0.pkg	✅ Available
Linux (Debian/Ubuntu)	gitperennial-v1.1.0.deb	✅ Available

Upgrading from v1.0.0: just run the new installer over your existing
install — no uninstall needed. Your database, tracked repos, history, and
license are all kept, and your existing GitHub token is carried over
automatically (see below).

See README.md
for install steps, and
QUICKSTART.md
for a guided tour of the dashboard.

What's new: multiple GitHub accounts

A GitHub personal access token only ever covers one owner — one personal
account or one organization. If your repos live under more than one (a
second account, a company organization, an enterprise organization), v1.0.0
could only track one of them. v1.1.0 lets you add a token for each owner,
and GitPerennial automatically uses the right one for each repo.

• New "GitHub accounts" section in Settings, above Tracked repos. Each
  account shows its token's status and expiration date, with a Manage
  button to replace or remove its token.
• See whose token it is before you save it. When you paste a token,
  GitPerennial checks it with GitHub right away and shows which account it
  belongs to.
• Classic and fine-grained tokens both work. A classic token covers
  every repo its account can reach, including organizations it belongs to,
  so one classic token is often all you need. A fine-grained token covers
  only the owner and repos it was given access to; if it was created for an
  organization, an optional "Owner name" field lets you say which one.
• Clear reasons when a repo can't be added — no account set up yet for
  that repo's owner, the token lacks push access (which GitHub requires for
  traffic data), or a fine-grained token that doesn't include that repo yet.
• Safer token replacement. Replacing an account's token now checks the
  repos you already track under that account, and warns you by name if the
  new token can't reach any of them — right when it happens, instead of as
  an unexplained sync failure later.
• Automatic upgrade. Your existing v1.0.0 token is moved into the new
  accounts list on first launch, under the account it belongs to. Nothing
  to re-enter, and no gap in tracking.
• Free tier unchanged: still one tracked repo, forever, no matter how
  many accounts you add.

Fixes

• A token that GitHub reports as lacking permission for a repo is no
  longer mistaken for a temporary rate limit and retried indefinitely. The
  repo is now flagged with the usual "no longer accessible" notice so you
  can see what's wrong and fix it.
• The "no longer accessible on GitHub" notices now list the real possible
  causes: the repo was deleted, renamed or transferred on GitHub, or the
  matching account's token no longer has access (expired, revoked, or
  replaced with a narrower one).
• Windows: Installed apps (Add/Remove Programs) now shows
  GitPerennial's real version number instead of 1.0.0.0.

Also fixed (all platforms)

• The background service now reliably restarts after an upgrade or
  repair install on Windows — it could previously stay silently
  stopped until the next reboot or a manual start.
• The tray icon now appears immediately after install or upgrade, on
  all three platforms — previously it could require logging out,
  restarting, or a manual launch before it showed up.
• The installer now clearly shows which version you're installing —
  in the Windows Setup wizard, the macOS Installer wizard, and Linux's
  dpkg/apt install output.
• macOS: the uninstaller now confirms which version it's removing.
• Windows: fixed a rare startup race where the background service,
  if it started before anyone had logged in (e.g. after an overnight
  reboot), could open the wrong, empty-looking database for that
  session instead of your real one. The service now correctly finds
  your real data on the very first start, with no manual step needed.

See CHANGELOG.md
for the full list.

Downloadable Assets are below:

GitPerennial v1.0.0

GitPerennial v1.0.0

Self-hosted GitHub traffic & release analytics that outlasts GitHub's
own 14-day history — clones, views, referrers, popular content,
release downloads, and issue metrics, kept forever, on your own
machine.

Downloads

Platform	File	Status
Windows	GitPerennial-v1.0.0.msi	✅ Available
macOS	GitPerennial-v1.0.0.pkg	✅ Available
Linux (Debian/Ubuntu)	gitperennial-v1.0.0.deb	✅ Available

See README.md
for install steps, and
QUICKSTART.md
for a guided tour of the dashboard once it's running.

What's in this release

See CHANGELOG.md
for the full list.

A note on this being a first release

This is GitPerennial's first public release. All three platforms have
been tested end-to-end on real hardware — a genuine fresh install, an
in-place upgrade, and the full background-service and tray/menu-bar
behavior, confirmed on real Windows, macOS, and Linux machines, not
just reviewed in code. macOS and Linux additionally had their full
licensing flow confirmed, including moving an active license from one
computer and operating system to another.

Downloadable Assets are below: