Skip to content

First release (v0.1.0): run the release workflow and prove the installers and incode update #18

Closed

Description

@blockmandev

Why

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)

  1. 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
  2. Watch Actions → release. Check that all 5 targets build and that the release has 5 archives plus SHA256SUMS.
  3. Install from the pre-release:
    • Linux/macOS: INCODE_VERSION=v0.1.0-rc.1 sh scripts/install.sh, then incode --version and sbx --version.
    • Windows: $env:INCODE_VERSION='v0.1.0-rc.1'; powershell -ExecutionPolicy Bypass -File scripts\install.ps1.
  4. 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.
  5. 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).
  6. 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

Generated by Claude Code

Activity

  1. blockmandev commented on Oct 23, 2026

    @blockmandev
    MemberAuthor

    First attempt: tag `v0.1.0-rc.1` pushed (run 39897604251). Nothing was published, because the release only goes out when every build succeeds.

    Target Result
    Windows x86_64 ✅
    macOS x86_64, aarch64 ✅
    Linux x86_64, aarch64 ❌ `libspa` 0.10.1 won't compile against Ubuntu 22.04's older PipeWire headers

    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.

  2. blockmandev commented on Oct 23, 2026

    @blockmandev
    MemberAuthor

    `v0.1.0-rc.2` is released and installs on every platform.

    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.

  3. added a commit that references this issue on Oct 24, 2026
  4. blockmandev commented on Oct 24, 2026

    @blockmandev
    MemberAuthor

    Done: incode v0.1.0 is released. https://github.com/incordai/Incode/releases/tag/v0.1.0

    Release run 40045910961, all green

    • Version check: the tag matches both crates (0.1.0).
    • Build: all 5 targets built (Linux x86_64 and aarch64 on Ubuntu 22.04, macOS x86_64 and aarch64, Windows x86_64).
    • Publish: it went out as a normal release. GitHub's releases/latest now points to v0.1.0.
    • Install check: it installed the release the way a user does, and each install checked its sha256 and reported incode 0.1.0 / sbx 0.1.0:
    Platform Installer Result
    Ubuntu 22.04 x86_64 install.sh ✅
    Ubuntu 22.04 arm64 install.sh ✅
    macOS install.sh ✅
    Windows install.ps1 ✅

    incode update proven end to end, on Windows, from a real v0.1.0-rc.2 install:

    before:                  incode 0.1.0-rc.2 / sbx 0.1.0-rc.2
    incode update --check -> incode v0.1.0 is available (this is 0.1.0-rc.2)
    incode update         -> incode updated 0.1.0-rc.2 -> v0.1.0 (incode-x86_64-pc-windows-msvc.zip, sha256 checked): …\incode.exe, …\sbx.exe
    after:                   incode 0.1.0 / sbx 0.1.0
    incode update --check -> incode 0.1.0 is up to date (latest: v0.1.0)
    

    The running programs were renamed to .old first, as designed for Windows.

    What it took:

    Unblocked: Homebrew, winget and Scoop manifests (tracked in #56).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions