Downloads

• Windows: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.2/QuiverLauncher-win-Portable.zip
• Linux x64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.2/QuiverLauncher-linux-x64.AppImage
• Linux ARM64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.2/QuiverLauncher-linux-arm64.AppImage
• macOS x64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.2/QuiverLauncher-osx-x64-Portable.zip
• macOS ARM64: https://github.com/tgeorgiadis/quiver/releases/download/v3.0.0-rc.2/QuiverLauncher-osx-arm64-Portable.zip

Quiver Launcher v3.0.0-rc.2 (prerelease)

Major packaging release: Quiver Launcher now ships with Velopack for self-update across Windows / Linux / macOS. Marked as a GitHub pre-release for testing. Not promoted to /releases/latest.

Changes since rc.1

• Rebranded to Quiver Launcher (QuiverLauncher pack id and binaries)
• Linux ships bare .AppImage downloads (no .tar.gz wrapper); mark executable after download
• Library app menus stay inside the window on far-right cards
• Linux/macOS startup no longer auto-applies shared Velopack updates across separate installs

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 .cmd on 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): QuiverLauncher-win-Portable.zip. Extract anywhere. Self-updating. Library data stays in the folder root (sibling of current/).
• Linux: QuiverLauncher-linux-*.AppImage (x64 / ARM64). Put it in its own folder (library files are created beside it), mark executable (chmod +x or file Properties), then run. Otherwise ~/.local/share/QuiverLauncher/ if that folder is not writable.
• macOS: QuiverLauncher-osx-*-Portable.zip (x64 / ARM64). Library beside QuiverLauncher.app when that folder is writable. Otherwise ~/Library/Application Support/QuiverLauncher/.

Also includes Velopack feed files (releases.*.json, .nupkg) required for in-app updates. Setup installers are omitted (portable-first).

Updates (3.0 and later)

• Self-update via Velopack and GitHub Releases (no separate updater helper exe or apply scripts)
• Prerelease Quiver Launcher updates: opt-in in Settings ╬ô├Ñ├å Advanced (Include prerelease Quiver Launcher updates). RC builds (version with -) already follow prereleases automatically.
• User data is never stored inside the replaced app content (current/, AppImage mount, or .app bundle)

App releases from GitLab

• Optional repositorySource on app entries (github default when omitted, or gitlab)
• 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 .\QuiverLauncher.exe
# Expect Status = Valid when signed builds are published