Chord Desktop 0.1.0-beta.3

The Flatpak sandbox gets no outside variables, so the Linux build shipped
with no GIF search key. CI now writes the CHORD_KLIPY_KEY secret into the
manifest, the same way it writes the version.

Linux: the .flatpak (it updates itself), or see https://bigaouette.com/chord-nightly/flatpak/. Windows: the -setup.exe. macOS (Apple silicon): the .dmg.

The macOS app is not notarized yet. If macOS says it cannot verify Chord, open System Settings → Privacy & Security and click Open Anyway.

b5ef7ac1a6778a9796f4d3a4133446c626cf2599f768e7b398a43fd603547958  Chord_0.1.0-beta.3_aarch64.app.tar.gz
2c48a6819303de926e4ffa3ea8df0dc5ddec49efa5b3d167c1de2f492828995b  Chord_0.1.0-beta.3_aarch64.dmg
23cd9aba02ed3d82c167ab4b70599c1a4f6cac7355ed60f990c328a84b4af359  Chord_0.1.0-beta.3_x64-setup.exe
cb68308f0c5d820a6bf89bc9dc7197d3b87f9ac313604b5a1272c069191ba6b6  Chord_0.1.0-beta.3_x86_64.flatpak

Chord Desktop 0.1.0-beta.2

Git keeps no empty folders, so the repository from gh-pages lacked refs/remotes and the second
publish failed with "opendir(refs/remotes): No such file or directory".

Linux: the .flatpak (it updates itself), or see https://bigaouette.com/chord-nightly/flatpak/. Windows: the -setup.exe. macOS (Apple silicon): the .dmg.

The macOS app is not notarized yet. If macOS says it cannot verify Chord, open System Settings → Privacy & Security and click Open Anyway.

1e72d682925eba1a764a40986ced772e7a178e797c6c3ea1ca0e94b022ef186b  Chord_0.1.0-beta.2_aarch64.app.tar.gz
601b1afc4d378ce0770dac3ce129581c5108330e92117f47cd57103961ca7072  Chord_0.1.0-beta.2_aarch64.dmg
17b1cf122b29567d389b7bc7da04d443dfd7f95c80649a1e942e5a2a84e2cf20  Chord_0.1.0-beta.2_x64-setup.exe
6cda205db0d9d93b8fc275ccf90832d6d591eaed36cdabd7ab79693ce5c72c50  Chord_0.1.0-beta.2_x86_64.flatpak

Chord Desktop 0.1.0-beta.1

Linux: .AppImage, .deb or .rpm. Windows: the -setup.exe. macOS (Apple silicon): the .dmg.

da052015709b1b1972c538ce0139fda796f321457a0b6a2577d3db22930d7cb8  Chord-0.1.0-beta.1-1.x86_64.rpm
ec552b3c868a55838d7c35e42410852bf6efdacc91020eb00a45edb732023a40  Chord_0.1.0-beta.1_aarch64.app.tar.gz
fbe22b1606d58b4c74750451445faa40ea263aa6f03a04163c58b383f15746ee  Chord_0.1.0-beta.1_aarch64.dmg
f665ed45bed18f5075d7b3e938351153d76c9876f88e087803166f18c1b47648  Chord_0.1.0-beta.1_amd64.AppImage
9797762b39a1b32c261d098bbe6413f6b121419bae9467044b91529318a1ca98  Chord_0.1.0-beta.1_amd64.deb
90c445c24041b6b05c98ed4638f6b443d903d24fd7b805f31c154d16c7a6c0e4  Chord_0.1.0-beta.1_x64-setup.exe

macOS: this build is not signed. If macOS says "Chord is damaged and can't be opened", it is not damaged: move Chord to Applications, then run this once in Terminal:

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

The next builds are signed ad hoc, so macOS offers "Open Anyway" in System Settings → Privacy & Security instead.