Quiver v3.0.0-rc.1
Pre-releaseDownloads
Install these (portable-first). Other assets on this release are Velopack update feed files.
- Windows: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.1/Quiver-win-Portable.zip
- Linux x64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.1/Quiver-linux-x64.tar.gz
- Linux ARM64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.1/Quiver-linux-arm64.tar.gz
- macOS x64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.1/Quiver-osx-x64-Portable.zip
- macOS ARM64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.1/Quiver-osx-arm64-Portable.zip
Quiver v3.0.0-rc.1 (prerelease)
Major packaging release: Quiver now ships with Velopack for self-update across Windows / Linux / macOS. Marked as a GitHub pre-release for testing. Not promoted to /releases/latest.
Breaking: upgrading from 2.4.x
In-app update from 2.4.2 or older cannot install Velopack 3.0. Download a fresh portable from this release and copy your library over manually.
See MIGRATING.md for what to copy (apps.json, settings.json, Apps/) and per-OS folder layouts.
Why Velopack?
- Standard self-updates across Windows, Linux, and macOS (replaces the custom zip-and-helper-script flow).
- Fewer false threat detections. The old helper script (for example a
.cmdon Windows) often tripped OS / antivirus heuristics. Velopack applies updates without that script. - Signed Windows builds. Packages are digitally signed. As reputation builds, SmartScreen warnings should become less common — though you may still see some early on.
Distribution
- Windows (primary):
Quiver-win-Portable.zip. Extract anywhere. Self-updating. Library data stays in the folder root (sibling ofcurrent/). - Linux:
Quiver-linux-*.tar.gz(x64 / ARM64) containing the AppImage in a folder. Extract, then run the AppImage. Library beside the AppImage when that folder is writable. Otherwise~/.local/share/Quiver/. - macOS:
Quiver-osx-*-Portable.zip(x64 / ARM64). Library besideQuiver.appwhen that folder is writable. Otherwise~/Library/Application Support/Quiver/.
Also includes Velopack feed files (releases.*.json, .nupkg) required for in-app updates. Setup installers are omitted (portable-first). Bare Linux AppImages are not published — use the .tar.gz.
Updates (3.0 and later)
- Self-update via Velopack and GitHub Releases (no separate
Quiver.Updater.exeor apply scripts) - Prerelease Quiver updates: opt-in in Settings → Advanced (Include prerelease Quiver updates). RC builds (version with
-) already follow prereleases automatically. - User data is never stored inside the replaced app content (
current/, AppImage mount, or.appbundle)
App releases from GitLab
- Optional
repositorySourceon app entries (githubdefault when omitted, orgitlab) - Add/Edit App includes a Repository Source dropdown (GitHub first)
- GitLab apps use gitlab.com release asset links hosted on GitLab only
- Optional GitLab API Token in Settings → Advanced
Windows signing
When Azure Artifact Signing is enabled, CI signs Windows packages during vpk pack using the GitHub Environment signing (OIDC subject repo:…/quiver:environment:signing).
Get-AuthenticodeSignature .\Quiver.exe
# Expect Status = Valid when signed builds are published