Releases: orkitec/orkige
Release list
Orkige 2.0.0-nightly.20260809+8a7155190
Editor version 2.0.0-nightly.20260809+8a7155190 - built 2026-08-09 (UTC) from
8a7155190, and only because the full test matrix on that
commit was green.
| Platform | Install | Portable | Build |
|---|---|---|---|
| macOS (Apple silicon) | Orkige-macos-2.0.0-nightly.20260809_8a7155190.dmg |
Orkige-macos-2.0.0-nightly.20260809_8a7155190.zip |
success |
| Linux (x86_64) | Orkige-linux-2.0.0-nightly.20260809_8a7155190.AppImage |
Orkige-linux-2.0.0-nightly.20260809_8a7155190.tar.gz |
success |
| Windows (x64) | Orkige-windows-2.0.0-nightly.20260809_8a7155190-setup.exe |
Orkige-windows-2.0.0-nightly.20260809_8a7155190.zip |
success |
Changes since b65199611
- The streak declarations have served (
8a715519) - The release create retries, with the delete inside the loop (
872c4eb2) - The browser-session job graduates from trial to gate (
69b5b986)
On macOS, open the .dmg and drag Orkige to Applications -
an app started from an unpacked download folder is subject to
macOS path randomization. On Windows the installer installs
for the current user only and needs no administrator rights.
On Linux the .AppImage is one file that carries the
libraries a distribution may not have installed:
chmod +x and run it (add --appimage-extract-and-run on a
distribution without FUSE).
The portable archives need neither and unpack anywhere.
Every download carries a VERSION file, a CHANGELOG.md and
a KNOWN-LIMITATIONS.md listing what this build cannot do
yet: read it first. The CHANGELOG.md asset beside the
archives is the FULL history - every version, fetchable
without unpacking anything.
The macOS app and disk image are Developer ID signed,
notarized by Apple and stapled, so they open with no
security prompt and need no quarantine flag cleared.
The Windows builds are UNSIGNED, so SmartScreen warns that it
does not recognise the publisher (loudest on the installer);
the limitations file gives those steps too.
The iOS Simulator player for this build is published as
orkige-player-ios-simulator-next-2.0.0-nightly.20260809_8a7155190.zip - Orkige downloads it itself when you
switch that platform on under Settings > Build Targets.
The Android player for this build is published as
orkige-player-android-next-2.0.0-nightly.20260809_8a7155190.zip - Orkige downloads it itself when you
switch that platform on under Settings > Build Targets.
Each asset has a .sha256 file beside it - verify a
download before trusting it.
Reference: Docs/nightly-builds.md.
Orkige 2.0.0-nightly.20260809+8a7155190
Editor version 2.0.0-nightly.20260809+8a7155190 - built 2026-08-09 (UTC) from
8a7155190, and only because the full test matrix on that
commit was green.
| Platform | Install | Portable | Build |
|---|---|---|---|
| macOS (Apple silicon) | Orkige-macos-2.0.0-nightly.20260809_8a7155190.dmg |
Orkige-macos-2.0.0-nightly.20260809_8a7155190.zip |
success |
| Linux (x86_64) | Orkige-linux-2.0.0-nightly.20260809_8a7155190.AppImage |
Orkige-linux-2.0.0-nightly.20260809_8a7155190.tar.gz |
success |
| Windows (x64) | Orkige-windows-2.0.0-nightly.20260809_8a7155190-setup.exe |
Orkige-windows-2.0.0-nightly.20260809_8a7155190.zip |
success |
Changes since b65199611
- The streak declarations have served (
8a715519) - The release create retries, with the delete inside the loop (
872c4eb2) - The browser-session job graduates from trial to gate (
69b5b986)
On macOS, open the .dmg and drag Orkige to Applications -
an app started from an unpacked download folder is subject to
macOS path randomization. On Windows the installer installs
for the current user only and needs no administrator rights.
On Linux the .AppImage is one file that carries the
libraries a distribution may not have installed:
chmod +x and run it (add --appimage-extract-and-run on a
distribution without FUSE).
The portable archives need neither and unpack anywhere.
Every download carries a VERSION file, a CHANGELOG.md and
a KNOWN-LIMITATIONS.md listing what this build cannot do
yet: read it first. The CHANGELOG.md asset beside the
archives is the FULL history - every version, fetchable
without unpacking anything.
The macOS app and disk image are Developer ID signed,
notarized by Apple and stapled, so they open with no
security prompt and need no quarantine flag cleared.
The Windows builds are UNSIGNED, so SmartScreen warns that it
does not recognise the publisher (loudest on the installer);
the limitations file gives those steps too.
The iOS Simulator player for this build is published as
orkige-player-ios-simulator-next-2.0.0-nightly.20260809_8a7155190.zip - Orkige downloads it itself when you
switch that platform on under Settings > Build Targets.
The Android player for this build is published as
orkige-player-android-next-2.0.0-nightly.20260809_8a7155190.zip - Orkige downloads it itself when you
switch that platform on under Settings > Build Targets.
Each asset has a .sha256 file beside it - verify a
download before trusting it.
Reference: Docs/nightly-builds.md.
Orkige 2.0.0-nightly.20260808+027e5076b
Editor version 2.0.0-nightly.20260808+027e5076b - built 2026-08-08 (UTC) from
027e5076b, and only because the full test matrix on that
commit was green.
| Platform | Install | Portable | Build |
|---|---|---|---|
| macOS (Apple silicon) | not produced | not produced | failure |
| Linux (x86_64) | not produced | not produced | failure |
| Windows (x64) | not produced | not produced | failure |
Recent changes
No previous nightly to compare against, so this lists the most recent 20 commits.
- The gate's lead comment states the model it now implements (
027e5076) - The binaries gate asks the one question protection cannot (
f8a79a6b) - The binaries floor is the required-context count, moved with reshapes (
1485da13) - The binaries gate retries its queries before conceding a night (
d1dabedd) - The look declaration returns to empty (
a69c2a91) - The binaries gate reads what its token can (
20dedfd8) - The distfile mirror goes (
b2ad9afd) - The lake declarations scope to next (
14bc101d) - The declaration matches the movers exactly (
4381406d) - Every distfile consults our asset mirror first (
8d24b891) - The configure wrapper prints what it resolves for the distfile seed (
53133edc) - The distfile seed reports loudly either way (
154c6d5e) - The lua distfile rides our ci-assets release (
6fe83168) - One if per step (
ad97f1a6) - The inaugural look declaration (
d591d368) - Every cache pin returns to v4, by SHA this time (
440bb3d2) - The mirror reflects the same sky on both flavors (
5fe4d7b3) - No pixel moves without a commit declaring it (
ba1377f1) - The cache action returns to v4 (
30ead278) - The mirror water is the same lit surface on both flavors (
18075f74)
On macOS, open the .dmg and drag Orkige to Applications -
an app started from an unpacked download folder is subject to
macOS path randomization. On Windows the installer installs
for the current user only and needs no administrator rights.
On Linux the .AppImage is one file that carries the
libraries a distribution may not have installed:
chmod +x and run it (add --appimage-extract-and-run on a
distribution without FUSE).
The portable archives need neither and unpack anywhere.
Every download carries a VERSION file, a CHANGELOG.md and
a KNOWN-LIMITATIONS.md listing what this build cannot do
yet: read it first. The CHANGELOG.md asset beside the
archives is the FULL history - every version, fetchable
without unpacking anything.
The macOS build is UNSIGNED, so macOS refuses the app
until its quarantine flag is cleared; its
KNOWN-LIMITATIONS.md gives the exact steps.
The Windows builds are UNSIGNED, so SmartScreen warns that it
does not recognise the publisher (loudest on the installer);
the limitations file gives those steps too.
The iOS Simulator player for this build is published as
orkige-player-ios-simulator-next-2.0.0-nightly.20260808_027e5076b.zip - Orkige downloads it itself when you
switch that platform on under Settings > Build Targets.
No Android player was published for this build
(failure), so this build cannot package for it.
Each asset has a .sha256 file beside it - verify a
download before trusting it.
Reference: Docs/nightly-builds.md.
Orkige 2.0.0-nightly.20260802+6b7f096dc
Editor version 2.0.0-nightly.20260802+6b7f096dc - built 2026-08-02 (UTC) from
6b7f096dc, and only because the full test matrix on that
commit was green.
| Platform | Install | Portable | Build |
|---|---|---|---|
| macOS (Apple silicon) | Orkige-macos-2.0.0-nightly.20260802_6b7f096dc.dmg |
Orkige-macos-2.0.0-nightly.20260802_6b7f096dc.zip |
success |
| Linux (x86_64) | Orkige-linux-2.0.0-nightly.20260802_6b7f096dc.AppImage |
Orkige-linux-2.0.0-nightly.20260802_6b7f096dc.tar.gz |
success |
| Windows (x64) | Orkige-windows-2.0.0-nightly.20260802_6b7f096dc-setup.exe |
Orkige-windows-2.0.0-nightly.20260802_6b7f096dc.zip |
success |
Recent changes
No previous nightly to compare against, so this lists the most recent 20 commits.
- Windows (
6b7f096d) - CLAUDE.md (
daf1fb0b) - iOS classic CI builds the host exporter (
fcbbd1c9) - Web export via a game pak (
a3f2f00c) - Lottie cook in C++ (
25898f61) - The exporter comes from where the payload does (
f80c80d5) - iOS and Android export in C++ (
b6bc136f) - macOS export in C++ (
c6f2c34e) - Exporter port, foundations and the texture cook (
3c50abe2) - Export works from a downloaded editor (
49f1f237) - A release is only published when the tree actually moved, so the dated archive was never growing with the calendar - it… (
2b5d43ad) - A gate that only fires where nobody can reproduce it has to carry its own evidence (
7063bdbc) - Seventeen years of ordinary development days were being presented as seventeen years of releases (
ed9fe2ae) - The attribution comes off the download page again (
e432b587) - The download page names the certificate authority before there is a certificate (
31ac9354) - A running application cannot replace itself, so the editor's updater never tries (
6f8ca06a) - The download button cannot name a file whose name changes nightly, so it names the release and lets the page improve it… (
d8e4c555) - A separator can belong to the FORMAT rather than to the machine (
3cc29ed0) - A tarball's filename promises less than the download needs, and the Linux nightly had been shipping that gap (
c4b3cdc2) - The interrupted gesture that edited anyway (
f66415e1)
On macOS, open the .dmg and drag Orkige to Applications -
an app started from an unpacked download folder is subject to
macOS path randomization. On Windows the installer installs
for the current user only and needs no administrator rights.
On Linux the .AppImage is one file that carries the
libraries a distribution may not have installed:
chmod +x and run it (add --appimage-extract-and-run on a
distribution without FUSE).
The portable archives need neither and unpack anywhere.
Every download carries a VERSION file, a CHANGELOG.md and
a KNOWN-LIMITATIONS.md listing what this build cannot do
yet: read it first. The CHANGELOG.md asset beside the
archives is the FULL history - every version, fetchable
without unpacking anything.
The macOS app and disk image are Developer ID signed,
notarized by Apple and stapled, so they open with no
security prompt and need no quarantine flag cleared.
The Windows builds are UNSIGNED, so SmartScreen warns that it
does not recognise the publisher (loudest on the installer);
the limitations file gives those steps too.
Each asset has a .sha256 file beside it - verify a
download before trusting it.
Reference: Docs/nightly-builds.md.