gogitup v0.6.0 was released on September 17, 2026. This update focuses on giving users finer control over authentication when checking and upgrading Go tools installed with go install. The headline improvement is per-app GitHub account selection, which lets you pin a specific stored GitHub CLI account to an individual tracked app. That makes it practical to separate work and personal accounts, access private repositories with a dedicated account, and avoid enabling global github_auth for all apps.

What’s new

Per-app GitHub account selection You can now specify a GitHub CLI account per tracked app. The new configuration field apps[].github_user pins an account for an app, and the CLI flags --github-user on add and install save the account at registration time. For apps with an explicit account, gogitup resolves tokens using gh auth token --hostname github.com --user USER without switching the active gh account, and rejects GH_TOKEN/GITHUB_TOKEN environment variables with guidance to unset them. Account selection works alongside private: true for authenticated release lookups and private source downloads, and gogitup list now shows a GitHub User column with JSON output including github_user.

Cache awareness Cache entries now record the GitHub account and privacy setting used for a check. Changing or removing github_user or toggling private invalidates the cache and triggers a fresh lookup. Account names are compared case-insensitively.

Improved error handling check and upgrade continue past per-app failures, report errors on stderr, and exit with status 1 if any app could not be processed. check --json still emits a valid JSON array, with failing apps showing latest_version: "unknown" and not being cached.

Documentation in CONFIG.md, USAGE.md, INSTALL.md, and EXAMPLES.md has been updated with per-app account examples and usage notes. Example usernames were updated for clarity.

Why it matters

Previously, authentication for GitHub-hosted tools was global. Users who maintain multiple GitHub CLI accounts or need private repository access for only some tools had to change the active account or enable broad tokens. With per-app selection, work and personal accounts can coexist in the same configuration, and private apps can use a dedicated account without affecting other tools. The change also makes it explicit which account is used for each app via list, improving visibility and auditability.

Upgrading

v0.6.0 is a non-breaking update. Existing configurations without github_user continue to use the existing github_auth and token resolution. To use per-app accounts, ensure GitHub CLI is installed and you are logged in for each account with gh auth login --hostname github.com. When an explicit account is set, unset GH_TOKEN and GITHUB_TOKEN to avoid rejection. Changing an app’s account or privacy setting will bypass cache on the next check; use gogitup check --force to refresh immediately.

Install or upgrade with your usual method for gogitup. See the project documentation at https://unitvectory-labs.github.io/gogitup/ for configuration details and examples.

This post was AI-generated. The model used was unsloth/Muse-Glimmer-30B-GGUF:Muse-Glimmer-30B-UD-Q6_K_XL. Reference repository UnitVectorY-Labs/gogitup, release v0.6.0, date of generation 2026-09-17. Author: release-storyteller.