wally-release

---
name: wally-release
description: Cut an Wally product release (independent of SDK version) — version bump, release:patch label, merge, auto-tag, bottles. Use when shipping wally after a published SDK kit, or when Homebrew / notarization / private overlays must not leak into public bottles.
---

# Wally release

Repo: `RunanywhereAI/wally`. Product version is `[product] version` in
`versions.toml` — CMake's `project(wally VERSION …)` reads it directly;
`Cargo.toml`'s `version` and `Formula/wally.rb`'s version stamp must match it
(`scripts/ci/check-versions.py`, and `build.rs` asserts the `Cargo.toml` /
`versions.toml` pair at build time). Independent of the SDK kit pin.

Do this **after** the SDK GitHub Release this pin targets is **published**
(not draft). Companion: **wally-kit-pin**, then this skill.

## 0. Facts

- Label form is `release:patch` / `release:minor` / `release:major` (**colon**).
  `.github/workflows/auto-tag.yml` matches that spelling only.
- Merge to `main` with that label → auto-tag pushes `v<CMakeLists VERSION>` and
  dispatches `release.yml`. Tag pushes with `GITHUB_TOKEN` do **not** trigger
  other workflows; the dispatch is required.
- Checkout in auto-tag uses `persist-credentials: true` so the tag push works.
- `release.yml` jobs: `macos` (macos-arm64 bottle), `windows-arm64` and
  `windows` (windows-x86_64 zip), `linux` (linux-x86_64 bottle), then `publish`
  assembles the GitHub Release. **macos runner must be macos-26** (Xcode 26 /
  Swift 6.2). macos-15 is Swift 6.1 and cannot resolve the SDK package;
  macos-14 is Swift 5.10.
- Public bottle / zip is OSS only. NeuRT / QHexRT overlays are workflow
  artifacts or `WALLY_PRIVATE_OVERLAY`, never public release assets, never
  Homebrew bottles.
- Linux bottles are not a v1 merge blocker.

## 1. Pin the SDK kit first

If this train needs new engines (sherpa routable, windows-arm64 kit, NeuRT
image gen): bump `cmake/sdk-pin.cmake` + CI `ref: v$SDK` in the **same PR**
(**wally-kit-pin**). CI must be green on that pin before you bump the product
version.

## 2. Product version + label

Next patch after `0.7.0` is `0.7.1`. Bump `versions.toml [product] version`,
`Cargo.toml`'s `version`, and any Formula version stamp in the same commit
(`scripts/ci/check-versions.py` fails the PR if they drift). Open/update the
PR and apply **exactly one** `release:patch` (or minor/major).

`gh pr create --label release:patch` is not atomic with the `opened` event —
verify the label landed (`gh pr view --json labels`).

## 3. CI bar before merge

Required: macOS product e2e (`scripts/test/e2e.sh ./build/wally`) and Windows e2e
against the pinned kit. `agents-sync.yml` must pass
(`scripts/ci/check-agents-sync.sh`).

Re-check immediately before merge (a rollup of SUCCESS can hide checks that
have not started):

```bash
gh pr checks <pr> --repo RunanywhereAI/wally --json name,state,bucket \
  --jq '[.[] | select(.state == null or .state == "")] | length'   # must be 0
```

Do not merge on a partial matrix. Confirm bypass eligibility the same way as
the SDK (`bypass_pull_request_allowances`) before `--admin`.

## 4. Merge triggers the release

```bash
gh pr merge <pr> --repo RunanywhereAI/wally --squash --admin   # only if allow-listed
```

`auto-tag.yml` tags `v$PRODUCT` and dispatches `release.yml`. Unlike the SDK
train, there is typically **no** pre-merge candidate to reuse — let this
release.yml run. Watch it; do not cancel `macos` for being "slow" (MLX host
link + e2e).

## 5. Verify the GitHub Release

```bash
gh release view v$PRODUCT --repo RunanywhereAI/wally --json isDraft,assets \
  --jq '{isDraft, names: [.assets[].name]}'
```

Expect `wally-$PRODUCT-macos-arm64.tar.gz`, `wally-$PRODUCT-windows-x86_64.zip`,
`wally-$PRODUCT-windows-arm64.zip`, and `wally-$PRODUCT-linux-x86_64.tar.gz`
(each + `.sha256`). **Must be empty** for `*neurt*`, `*qhexrt*`, `*private*`.

If `release.yml` still creates a non-draft release, that is the live product
cut — confirm asset names before anyone bottles from it. Stamp Formula from
the macOS sidecar (`scripts/release/stamp-formula.py`) when that path is wired.

## 6. Overlays after the public cut

Private packs stay off the public release. For a machine that should load
NeuRT / QHexRT:

```bash
export WALLY_PRIVATE_OVERLAY=/path/to/RunAnywhere-cpp-desktop-macos-arm64-neurt-private-v$SDK.tar.gz
# or windows-arm64-qhexrt
```

`WALLY_REQUIRE_PRIVATE=1` fails closed when the overlay is missing. Default CI
must pass without it.

Device proof is not CI: rebuild overlay `wally` on a Mac (NeuRT image gen) and
on Snapdragon ARM64 Windows (QHexRT). Match QAIRT to the device Hexagon skel
(`ADSP_LIBRARY_PATH`); see **wally-e2e**. Public `v0.5.1` bottles are OSS —
NeuRT/QHexRT will never appear in `wally backends` on those artifacts.

## Do not

- Attach `wally-*` assets onto an SDK GitHub Release.
- Pin `fetch-kit.sh` at a draft SDK tag.
- Ship NeuRT / QHexRT inside the public bottle "just this once".
- Use macos-14 or macos-15 for the Apple job (need macos-26 / Swift 6.2).
- Weaken `assert-backends.sh` when `HAS_SHERPA`/`HAS_ONNX` is TRUE.

More agent context in RunanywhereAI/RCLI

12 other files this repository gives its agents.