Aquesta és la versió actual. · Data de publicació:
Fitxers d’instal·lació v0.4.6
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) | Usuari actual | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
Viff 0.4.6 makes committing and conflict handling more direct: checked files can be committed from the working tree without staging first, and the conflict result pane is now editable; opening and refreshing large LFS repositories no longer waits for a file listing.
Highlights
This release joins "checked files are the commit scope" and "edit the conflict result in place" into one step, makes LFS file statistics run on demand, and gives the Project and Commit panels one shared width.
✨ New features
- Checking files in Changes now enables Commit or Commit and Push directly: their current working-tree content is committed, already-staged content in unchecked files stays staged, and modifications, deletions, untracked files, and staged renames all work in one commit.
- The middle Result pane of a conflict tab is editable: Accept Ours / Theirs / Both edits only the buffer as an undoable change, ⌘S writes it to disk, and Mark as Resolved remains an explicit user action.
⚡ Improvements
- LFS managed-file counts are now on demand: opening a repository and ordinary refreshes show the working-tree state first, and clicking the LFS marker or Git tool window's "Refresh LFS Statistics" lists the files and reports the last count time, staleness, or failure.
- The Commit panel always states the commit scope (checked files, unstaged content, unchecked staged content, partial staging) and asks for confirmation when a checked file has both staged and unstaged changes.
- Coalesced refresh requests keep their metadata scope, so a large repository triggers fewer consecutive full refreshes.
🛠 Fixes
- The left splitter no longer jumps when switching between the Project and Commit tabs; the two panel widths in older settings migrate to one shared width.
- Hovering a truncated reference label or its +N fold in the Log shows the complete local branch, remote branch, and tag names.
Upgrade instructions
- Upgrading from v0.4.5: the settings file migrates on load, folding projectPanelWidth / commitPanelWidth into leftPanelWidth; the first save writes only the new field, and older versions fall back to their own defaults if you downgrade.
- macOS: choose the Apple Silicon or Intel DMG, quit the old version, open the DMG, and replace Viff.app in Applications.
- Windows: quit the old version and run the x64 installer.
- Windows portable: extract the archive, enter its directory, and run viff.exe without installing.
- Debian/Ubuntu: run sudo apt install ./viff-v0.4.6-linux-amd64.deb.
- Linux portable: extract the archive, enter its directory, and run ./viff after installing the required system libraries.
- Install Git separately on PATH, and check the release guide for Linux dependencies.
Compatibility and known issues
- LFS file counts reflect the last explicit count only; when HEAD or staged content changes, the previous number stays with a stale marker until the LFS marker or the menu action is used again.
- Checked-file commits are unavailable during a merge or cherry-pick; clicking a row also checks it, so previewing a diff narrows the commit scope; submodules, sparse-checkout, and split index have no separate handling.
- The conflict result pane does not yet offer a base-ancestor pane or one-click application of non-conflicting changes; a successful save rebuilds the view and clears the result pane's undo history and caret position.
- macOS requires version 13 or later; Linux needs a working graphical session, rendering backend, and the system libraries listed in the release guide.
- The macOS app is ad-hoc signed without Developer ID signing or notarization; the Windows installer is not Authenticode signed, so the system may show a security prompt; remote repositories remain read-only observation.
- Install only files from the project release page after checking their checksums; verify the source if the operating system blocks them.