Pre-releasev0.1.0 is not published yet — Tauri v2, Rust and SQLite·Build status →
reqtone / download

ReqTone v0.1.0 is not released yet

There is nothing to download from this page today, and we would rather say so plainly than leave buttons here that go nowhere. Below is where each platform actually stands and what has to happen before the first binaries go up.

version v0.1.0published nonesigned not yet
Build status

Where each platform stands

Updated by hand as things move. If a platform is not listed as published, no installer for it exists anywhere.

Windows

Builds, not published

Windows 10 (1809+) or 11 · x64 · WebView2 runtime

Planned artefacts
.msi installer and .exe standalone
Today
The installer builds today. Nothing has been published, and the build is not code-signed.

macOS

Build job unverified

macOS 11 Big Sur or newer · Apple Silicon and Intel

Planned artefacts
One universal .dmg covering both architectures
Today
A build job exists but has not been confirmed to complete. There is one universal .dmg, not a separate Intel and Apple Silicon download.

Linux

No pipeline yet

Ubuntu 20.04+, Fedora 36+, Arch · webkit2gtk-4.1 runtime

Planned artefacts
.AppImage and .deb
Today
Neither bundle has ever been built. Linux packages have to be built on Linux and that job does not exist yet.
Before you get it

The first builds will be unsigned

Worth knowing now rather than meeting it as a warning dialog.

Code signing is not configured yet on any platform. Until a Windows certificate and an Apple Developer ID are in place, the installers we publish will be unsigned, which means Windows SmartScreen will interrupt the install and macOS Gatekeeper will refuse to open the app on the first try.

When the first release goes up, this page will carry the exact steps to get past both, and a SHA-256 checksum for every file so you can confirm you have what we published rather than something that replaced it in transit.

Note
Checksums are generated by the release job from the published file and written to this page from that output. They are never typed by hand, so a missing hash is possible and a wrong one is not.
What has to happen

The order of work

No date attached, because the signing step is the one that cannot be estimated honestly yet. This page changes when that changes.

01

A green test run

The test suite has to pass end to end before anything is cut as a release.

02

Windows and Linux build jobs

Windows builds locally today but is not automated. Linux has no pipeline at all — those bundles have to be produced on Linux.

03

Code signing

This is the long pole, not the builds. Windows needs a purchased certificate and Apple needs a Developer ID with notarisation. Everything before this is days; this is not.

In the meantime

Read what it actually does.

The features and docs describe the app as it exists today. Nothing on those pages depends on a download.

v0.1.0 · not released yet · Windows, macOS and Linux planned