Desktop updater
Needs attentionVersion --
Target --
Build time --
Signature missing
Pubkey present
Release operations
RavenVPN update feeds
Monitor the live update feed, verify download signatures, and keep the desktop fleet on trusted builds.
Feed health
High-level indicators for the updater and downloads endpoints.
Downloads
Needs attentionWindows --
Host --
SHA --
Update feed detail
Keep signatures present so the desktop client can verify upgrades.
Updater endpoint
Control plane URL for update metadata.
Release metadata
Version: --
Published: --
Target: --
Installer URL
Primary asset used by the updater.
Signature
Required for trusted updates.
--
Updater pubkey
Used by clients to verify update signatures.
dW50cnVzdGVkIGNvbW1lbnQ6IG1pbmlzaWduIHB1YmxpYyBrZXk6IDQ4QkQ4NjdB...
Download feed detail
Direct download metadata for the website and distribution portals.
Downloads endpoint
Control plane URL for client downloads.
Windows package
Version: --
Available: no
Notes: --
Checksum
SHA256 for manual validation.
--
Installer URL
Primary Windows download.
Release notes
Keep a short summary of what changed with each build.
Update notes
No notes published yet.
Download notes
No notes published yet.
Verification commands
Copy-ready commands for release validation.
Fetch update feed (curl + jq)
Confirm update metadata quickly.
curl -s http://127.0.0.1:18080/v1/updates/desktop/windows | jq .
Fetch downloads feed (curl + jq)
Verify download metadata quickly.
curl -s http://127.0.0.1:18080/v1/downloads | jq .
Verification checklist
Recommended steps before announcing a new build.
Validate checksum
Run certutil -hashfile RavenVPN-Setup.exe SHA256 and match SHA.
Confirm signature
Ensure updater signature is present for the active platform.
Dry-run client update
Use the desktop "Check updates" button in dev to confirm availability.
Raw JSON preview
Copy and inspect the payloads served by the control plane.
Updater JSON
http://127.0.0.1:18080/v1/updates/desktop/windows
Downloads JSON
http://127.0.0.1:18080/v1/downloads