Skip to content

feat(cli): self-contained aexp binaries, install script and binary adoption proof (story 29.3) - #238

Merged
fabbrik merged 1 commit into
mainfrom
feat/29-3-aexp-binaries
Nov 16, 2026
Merged

fabbrik merged 1 commit into
mainfrom
feat/29-3-aexp-binaries

Conversation

@fabbrik

@fabbrik fabbrik commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Story 29.3 of Epic 29 (reach without a .NET toolchain): aexp without the .NET SDK.

What

  • Binaries. eng/publish-binaries.sh builds single-file, self-contained aexp for linux-x64, linux-arm64, osx-arm64, osx-x64 and win-x64 from a locked restore of the Cli project's own packages.binaries.lock.json (conditional on AexpBinaries, so a plain build, restore or pack never sees it and the tool package is byte-for-byte unchanged; verify-packages still passes). No trimming or AOT.
  • Release. verify builds and checks them (six files, sha256sum --check --strict, the Linux binary prints the tagged version), appends a ## Binaries section with the sums to the notes, and uploads them; publish checks the sums again and attaches them to the GitHub release (a re-run completes an existing release's assets with --clobber).
  • Install script. scripts/install-aexp.sh (curl -fsSL .../main/scripts/install-aexp.sh | sh, POSIX sh): detects the platform, picks the newest release (AEXP_VERSION pins one, AEXP_DOWNLOAD_BASE replaces the release URL), verifies the SHA-256 sum against SHA256SUMS before installing anything, puts aexp in ~/.local/bin (AEXP_INSTALL_DIR).
  • Proof. eng/prove-adoption-path.sh --binaries <dir> runs the install script against a local file:// base (a copy with a corrupted sum first, which must install nothing), then the 29.2 checks, with no dotnet call. CI: job binaries plus five adoption-path-binary (<rid>) legs on ubuntu-24.04, ubuntu-24.04-arm, macos-15, macos-15-intel, windows-2025, none with the SDK installed.
  • Pinned. WorkflowTests: the two CI jobs, the release rules (19 new mutation rows), the scripts (executable, runtimes equal to the csproj's list, sum checked before mv).
  • Docs: README, CLI guide, Claude Code guide and the package README lead with the no-.NET path; RELEASING (step 7a), CONTRIBUTING, CHANGELOG.

Review

One edge-case reviewer: 17 findings, 4 patched (install script: empty version after a failed --version, a leading v in AEXP_VERSION, a raw mv failure, the rate-limit message), the rest false or rejected with evidence; nothing deferred.

After merge

The binaries exist from the first release after this change; until then the install script fails naming the missing asset. The five legs and binaries join the required checks after the first green run on main.

🤖 Generated with Claude Code

…ry adoption proof (story 29.3)

The release attaches single-file, self-contained aexp binaries for linux-x64, linux-arm64, osx-arm64, osx-x64 and
win-x64 with SHA256SUMS (sums quoted in the notes), built by eng/publish-binaries.sh from a locked restore of the Cli
project's own binaries lock file, so the tool package is untouched. scripts/install-aexp.sh (curl | sh) picks the
binary for the machine, verifies its sum and puts it on PATH. CI builds the same binaries on every pull request and
proves each on its own runner with no .NET installed, through the install script (a corrupted sum refused first) and
the 29.2 adoption-path checks. WorkflowTests pin the jobs, the release rules and the scripts. The README leads with
the path that needs no .NET.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@fabbrik
fabbrik merged commit 4e8fb2d into main Nov 16, 2026
122 of 128 checks passed
@fabbrik
fabbrik deleted the feat/29-3-aexp-binaries branch November 16, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant