You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First release (v0.1.0): run the release workflow and prove the installers and incode update #18
Everything needed to ship binaries is in main but has never run for real:
.github/workflows/release.yml;
scripts/install.sh and scripts/install.ps1;
incode update (src/self_update.rs).
Only a pushed v* tag runs the workflow.
What exists
release.yml runs on a v* tag and builds incode + sbx for:
x86_64/aarch64-unknown-linux-gnu (on ubuntu-22.04 and ubuntu-22.04-arm),
x86_64/aarch64-apple-darwin,
x86_64-pc-windows-msvc.
Packaging:incode-<target>.tar.gz (.zip on Windows), holding incode, sbx, LICENSE, NOTICE and README at the top level, plus a SHA256SUMS file. Published with softprops/action-gh-release@v2; a tag containing - is marked as a pre-release.
install.sh (POSIX sh) detects the OS and arch, checks the download against SHA256SUMS, and installs to ~/.local/bin or $INCODE_INSTALL_DIR. INCODE_VERSION pins a version.
install.ps1 installs to %LOCALAPPDATA%\incode\bin and adds it to the user PATH. It has never been run or even syntax-checked (no PowerShell where it was written).
incode update [--check] reads the latest release from the GitHub API, compares versions, downloads, checks the hash against SHA256SUMS, and swaps the binary in by rename. On Windows the running exe is renamed to .old first. It also replaces sbx when it sits beside incode.
Steps (local)
Try a pre-release first, so nothing is offered as stable:
git checkout main && git pull
git tag v0.1.0-rc.1 && git push origin v0.1.0-rc.1
Watch Actions → release. Check that all 5 targets build and that the release has 5 archives plus SHA256SUMS.
Install from the pre-release:
Linux/macOS: INCODE_VERSION=v0.1.0-rc.1 sh scripts/install.sh, then incode --version and sbx --version.
Check incode update --check, which reads releases/latest. A pre-release is not "latest", so expect "no published release" until a stable tag exists. That is fine.
If everything works: git tag v0.1.0 && git push origin v0.1.0. Then, from an older build, run incode update and check that it swaps in place (including Windows, where the exe is in use).
Delete the rc release and tag if you don't want them kept.
Known caveats
Linux runtime libraries: the Linux binaries need libgbm, libwayland-client and libxcb at run time (desktop capture is on by default). A server build without the desktop-capture feature would need its own target.
Windows on ARM: there is no aarch64 Windows build; install.ps1 installs the x86_64 build, which runs under emulation.
Archive layout: the archive must not contain ./ entries, because the unpacker refuses them. release.yml lists the files by name for that reason.
Done when
Release workflow green for all 5 targets
install.sh works on Linux and macOS; install.ps1 works on Windows
incode update upgrades a real older build on each OS
Cause: xcap 0.9.8, the screen-capture crate, always builds a Wayland/PipeWire backend on Linux, which incode never uses (Linux computer use is X11 only). Regular CI builds on the newest Ubuntu, so it never saw this.
Fix (owner's choice): capture the X11 screen with `x11rb`, which is already a dependency, and keep xcap only for Windows and macOS. Ubuntu 22.04, Debian 12 and RHEL 9 stay supported. A CI job that builds the way the release does is being added, so this can't recur. The next try will be `v0.1.0-rc.2` on the fixed main.
Left: `incode update` can't be proven against a pre-release, because GitHub's "latest release" skips them. It needs the first final tag (`v0.1.0`), which is the owner's call.
Activity
blockmandev commentedon Oct 23, 2026
First attempt: tag `v0.1.0-rc.1` pushed (run 39897604251). Nothing was published, because the release only goes out when every build succeeds.
Cause: xcap 0.9.8, the screen-capture crate, always builds a Wayland/PipeWire backend on Linux, which incode never uses (Linux computer use is X11 only). Regular CI builds on the newest Ubuntu, so it never saw this.
Fix (owner's choice): capture the X11 screen with `x11rb`, which is already a dependency, and keep xcap only for Windows and macOS. Ubuntu 22.04, Debian 12 and RHEL 9 stay supported. A CI job that builds the way the release does is being added, so this can't recur. The next try will be `v0.1.0-rc.2` on the fixed main.
desktop::capture::x11: copy the root Visualtype rather than clone it …
ci: live-x11-capture runs the X11 capture test under Xvfb at depth 24…
Merge pull request #57 from incordai/fix/linux-x11-capture
Merge pull request #58 from incordai/release/v0.1.0-rc.2
Merge pull request #59 from incordai/ci/install-check
blockmandev commentedon Oct 23, 2026
`v0.1.0-rc.2` is released and installs on every platform.
Release run 39965646984: the new tag/version check passed, all 5 targets built, and the release was published as a pre-release with 5 archives plus `SHA256SUMS`. https://github.com/incordai/Incode/releases/tag/v0.1.0-rc.2
Install check (ci: install each published release the way users do (refs #18) #59, run 39968703816): the release was installed with that tag's own installers, and each install checked its sha256 and reported `incode 0.1.0-rc.2` / `sbx 0.1.0-rc.2`.
It also passed by hand on the owner's Windows machine, which got its user PATH restored afterwards.
Fixes this took:
Left: `incode update` can't be proven against a pre-release, because GitHub's "latest release" skips them. It needs the first final tag (`v0.1.0`), which is the owner's call.
Merge pull request #66 from incordai/release/v0.1.0
blockmandev commentedon Oct 24, 2026
Done: incode v0.1.0 is released. https://github.com/incordai/Incode/releases/tag/v0.1.0
Release run 40045910961, all green
releases/latestnow points tov0.1.0.incode 0.1.0/sbx 0.1.0:install.shinstall.shinstall.shinstall.ps1incode updateproven end to end, on Windows, from a realv0.1.0-rc.2install:The running programs were renamed to
.oldfirst, as designed for Windows.What it took:
Unblocked: Homebrew, winget and Scoop manifests (tracked in #56).