Repository navigation
INT-04: compiler distribution strategy (native OCaml binary — not JSR/npm) #260
Description
Split out of #181. Packaging prep (docs/PACKAGING.adoc) made the JS runtime packages JSR-publishable (@hyperpolymath/affine-js, @hyperpolymath/affinescript-tea — manual workflow scaffolded, not yet published). But #181 also says "publish compiler", and the compiler is a native OCaml binary, not a JSR/npm package.
Decision needed (one-way-door)
How is the compiler distributed so consumers (and affinescript-lsp, INT-10) can install it?
Options:
- GitHub Releases binaries — per-platform artifacts via the existing
release.yml(v*tags); install script / fetch-pin. - Guix/Nix channel — aligns with the repo's primary packaging (
guix.scm/flake.nix); reproducible, but narrower audience. - Thin JSR/npm shim — a small package that downloads a pinned, checksummed prebuilt binary on install (gives
deno/npmergonomics without shipping OCaml source). - Combination (e.g. 1 + 3).
Why filed, not guessed
Irreversible-ish (sets the install contract + the LSP distribution path, INT-10) and outside the bounded packaging-prep scope. The JS-package publish path is ready and independent of this.
Refs #181. Blocks INT-10 (affinescript-lsp distribution).
Activity
chore(packaging): INT-04 JSR packaging prep — runtime publish-ready, …
docs(adr): ADR-019 — compiler distribution: Releases + thin Deno/JSR …
ci(release): #260 S2 — per-platform compiler binaries + SHA256SUMS (A…
feat(cli): #260 S3 — @hyperpolymath/affinescript compiler shim (ADR-019)
feat(cli): #260 S3 — @hyperpolymath/affinescript compiler shim (ADR-019…
feat(lsp): INT-10 — affinescript-lsp resolves compiler via ADR-019 sh…
feat(shim): #260 S4 — finalise pins.js for v0.1.0 (partial), bump shi…
ci(release): swap retired macos-13 runner for macos-15-intel (#292)
feat(shim): close INT-10 — pin v0.1.1 (full coverage), bump shim 0.1.2 (
feat(doc-truthing): in-repo DOC-04/05 guard + ADR-019 record (#476)
fix(release): restore release binaries — immutable-release draft flow…