Downloads and rolling releases

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

Beskid does not ask you to compile from source on day one unless you want to. The public site publishes rolling CLI builds tied to compiler CI, not hand-edited patch bumps in a README.

Rolling CLI channels

The beskid superrepo GitHub Actions release workflow publishes prebuilt binaries to GitHub Releases on beskid_compiler (cli-stable/cli-unstable, cli-version.txt, immutable cli-v*). Version resolution, matrix builds, provenance, and promotion use repository scripts plus reusable GitHub Actions workflows. Install scripts under the website (site/website/public/) and the Downloads page consume a channel-specific rolling tag.

accTitle: Compiler release to download page
accDescr: Compiler CI creates release assets, then the website publishes the verified version and install choices.
flowchart TD
  subgraph ci [Compiler CI]
    T[Git tags v*] --> V[Release workflow resolves channel + rolling semver]
    V --> B[Build matrix binaries]
    B --> R[Release cli-stable / cli-unstable + cli-version.txt]
  end
  R --> S[site sync:cli-version]
  S --> D[Downloads page + install scripts]

Text equivalent: Compiler CI resolves a tagged release channel, builds the platform binaries, and publishes the release assets. The website then reads the release metadata and shows the matching download and install choices.

The website can sync displayed version from GitHub via pnpm sync:cli-version (see packages/trudoc/scripts/sync-cli-version.mjs), which updates site/website/src/data/cli-version.json and aligns compiler/crates/beskid_cli/Cargo.toml when you develop in the superrepo.

What you get per platform

Typical release artifacts include the beskid CLI for common OS/arch pairs (Linux, macOS, Windows—exact matrix follows CI). Platform packages (.deb, .msi, .dmg, Homebrew) and container images are also available; see Downloads for the full list.

User-facing docs may also mention cdn.beskid-lang.org for direct binary fetch; treat the Downloads page as the curated entry.

Pinning vs living on the edge

Situation	Recommendation
Local hacking	Rolling cli-stable/cli-unstable is fine; re-run install when things break mysteriously.
CI for your app repo	Pin a known version string from cli-version.txt or cache a specific release asset; document the pin in your pipeline.
Reproducing a bug report	Record beskid --version and the git commit of the compiler if built locally.

Normative pointers

• CLI distribution and install (platform spec tooling area)
• Downloads page — install tabs and command blocks

Next

Install scripts and PATH