Repository navigation
Releases
Releases · artifactdev/gitnexia
GitNexia 1.8.0
Added
- Per-account SSH management. Each profile can select an existing SSH key or generate
an Ed25519 key (RSA for Azure DevOps), with an optional passphrase. Dedicated keys override
system identities and the SSH agent for matching remotes. Public keys can be registered
using the account's token on GitHub, GitLab, Forgejo and Bitbucket, with explicit errors
and manual copy/registration when permissions or server policy prevent uploads. - System SSH settings. Inspect, edit or clear the user's SSH configuration with confirmation
and backups, and remove Git's global SSH command. Private key files are never deleted.
GitNexia 1.7.9
Fixed
- Bitbucket HTTPS authentication. Clone, fetch, pull and push now use the active profile's
selected Bitbucket Data Center / Server account and personal access token. Custom HTTPS ports
and installation context paths are respected; SSH continues to use existing keys.
GitNexia 1.7.8
Changed
- GitHub HTTPS authentication. Git operations use the active profile's selected GitHub
account when configured. GitHub tokens need access to the repository, including Contents
write permission for pushes; SSH continues to use your existing SSH configuration.
Fixed
- Git identity display. Settings refreshes the displayed commit identity after a profile
switch or an edit to the profile's name, email or extra Git config.
GitNexia 1.7.7
Fixed
- AI CLI runtime lookup. Commands configured with an executable path now include its
directory in the child process'sPATH, so tools such as GitHub Copilot CLI installed through
NVM can find a siblingnodeexecutable even when it is missing from the app'sPATH.
GitNexia 1.7.6
Added
- Git setup guidance. When Git is missing, GitNexia shows operating-system-specific
installation instructions, a link to the official download page and an option to check again.
Too-old or unstartable Git installations show separate messages.
GitNexia 1.7.5
Changed
- Open in editor toolbar placement. Moved the button to the right-hand group beside Actions
and Search. The main button opens the project in the default or last-used editor; the dropdown
arrow selects another editor. - GitNexia-only build assets. Linux, Windows and macOS release builds no longer produce
duplicate packages under the old GitNex names. Migration from existing installations is unchanged.
GitNexia 1.7.4
Added
- Open repository in editor. Open the whole active worktree folder in an installed editor
such as VS Code or Zed from the toolbar, repository tab menu or command palette.
GitNexia 1.7.3
Added
- Azure DevOps inline pull-request comments. Compare a PR's net changes from its common base
to its head, and post comments on lines in the diff. Comments post immediately; batched draft
reviews are not supported.
GitNexia 1.6.1
Changed
- 1.6.1 publishes only the GitNexia package names. The pre-rename
GitNex_*copies that 1.6.0
carried for older installs are gone. A GitNex 1.5.x still finds and installs 1.6.0 under the old
names, and updates from there to 1.6.1; a fresh install takes 1.6.1 directly.
GitNexia 1.6.0
Changed
- GitNex is now GitNexia. The app, its bundles and packages, its repository
(artifactdev/gitnexia) and its website (https://artifactdev.github.io/gitnexia/) are
GitNexia. The first start copies GitNex's config, data, CEF profile and tokens to GitNexia's
folders and keyring service, and moves the UI'slocalStoragekeys over; the old folders and
keys stay, so a downgrade still finds them. Stack tables, Compare refs and an in-progress
interactive rebase written by GitNex are still recognized. The internal crates and binary are
gitnexia-*/gitnexia(Windows:GitNexia.exe), the bundle id iscom.gitnexia.desktop,
and the Linux packages replace thegitnexones. - Updates move to the new repository. 1.6.0 publishes its packages under both
GitNexia_*
and the oldGitNex_*asset names, and this version reads either; older builds may need a
manual install if GitHub's repository redirect doesn't carry them. - macOS releases are signed with an Apple Developer ID and notarized. Gatekeeper accepts the
.dmg's first launch, and the Team ID lets the Keychain's Always Allow carry over. The first
update signed with the new certificate asks once more for folder permissions; the ones after it
keep them (docs/releasing.md, "macOS signing").