Skip to content

Nightly Build — 2026-10-30 10:22 UTC

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Mar 22:19
· 475 commits to master since this release
nightly
de9cad5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Automated nightly build from master — commit 0b6117d2178175837766eec7fe5e628a7676b3bb.

🕐 Built: 2026-10-30 10:22 UTC

These are pre-release binaries built automatically. They may be unstable.

Downloads

Platform Package Requirements
Windows Flare-Windows-Portable-nightly.zip Windows 10/11 64-bit (x86_64/AMD64) — ARM is not supported
Linux Flare-x86_64.AppImage (standalone) or Flare-Linux-nightly.tar.gz x86_64 Linux, glibc 2.35+ (Ubuntu 22.04 or newer)
macOS Flare.dmg macOS 13+ Intel (Apple Silicon via Rosetta 2)

Windows usage

  1. Extract the ZIP — keep all files together in the same folder.
  2. Run Flare.exe from that folder.
  3. Do NOT move Flare.exe out of the folder — it needs the bundled DLLs and portablestuff/ to be in the same directory.

"DLL not found" / crashes on launch? Make sure you're on 64-bit Windows and haven't moved Flare.exe. If antivirus quarantined a DLL, whitelist the folder and re-extract.

macOS usage

  1. Open Flare.dmg.
  2. Drag Flare.app to your Applications folder.
  3. On first launch, right-click → Open (to bypass Gatekeeper on unsigned builds).

"Flare cannot be opened because the developer cannot be verified"? Right-click the app and choose Open, or go to System Preferences → Privacy & Security and click Open Anyway.

Icon shows a 🚫 badge, or macOS says the app "is damaged and can't be opened"? This is the download quarantine flag on an ad-hoc-signed build — common on Apple Silicon, and it gives you no entry in Privacy & Security to approve, so right-click → Open will not help. Clear the flag once in Terminal:

xattr -dr com.apple.quarantine /Applications/Flare.app

Then launch normally. (Flare is not yet notarized with an Apple Developer ID; until it is, every download needs this once.)

Linux usage

Easiest: download Flare-x86_64.AppImage, then:

chmod +x Flare-x86_64.AppImage
./Flare-x86_64.AppImage

Or the tarball: extract tar xzf Flare-Linux-nightly.tar.gz, then inside the
Flare-Linux-nightly/ folder run ./Flare.AppImage (or the Flare binary if
AppImage creation was skipped). If the standalone AppImage asset is absent, the
build's AppImage step failed — check the CI run for ::warning:: lines.

See the CI run for build logs and smoke test results.

Assets 7
Loading