Skip to content
This repository was archived by the owner on Oct 21, 2026. It is now read-only.

Rename the binary to al-runner and note AL Runner v2 on PATH - #395

Merged
StefanMaron merged 6 commits into
mainfrom
binary-al-runner
Oct 21, 2026
Merged

StefanMaron merged 6 commits into
mainfrom
binary-al-runner

Conversation

@StefanMaron

Copy link
Copy Markdown
Owner

The binary alrunner becomes al-runner (owner decision 2026-10-21, ADR-016). AL Runner v2's dotnet tool has the same command name, so v3 now tells the user when it finds another copy.

What changed

  • Name. [[bin]] name = "al-runner" in crates/alrunner-cli/Cargo.toml. --version prints al-runner 3.x (commit). Help text, error texts, CARGO_BIN_EXE_al-runner in the tests, and docs use the new name.
  • Release pipeline. build-packages.yml builds archives named al-runner-<label>-<target>. release-tag.yml checks that --version starts with al-runner $VERSION. release/smoke.sh and the release titles match.
  • Installers. install.sh and install.ps1 install al-runner. They still install a release from before the rename (up to 3.0.0-alpha.2) under its old name. They print a note when an old alrunner sits in the install folder, and when AL Runner v2 is in ~/.dotnet/tools. If v2's folder comes first on PATH, they say which order to use.
  • Note about another al-runner on PATH (crates/alrunner-cli/src/path_note.rs). Every command except serve, --help and --version looks for other al-runner files on PATH and in ~/.dotnet/tools. It skips itself and version-manager shims. It prints one line to stderr, at most once a day (a stamp file in the cache folder). Nothing goes to stdout.
  • --version lists each other copy after its own line, with the first line of that copy's --version. It waits at most 2 seconds per copy. A reader that takes only the first line does not cause an error.
  • ALRUNNER_NO_PATH_NOTE=1 turns the note and the list off.
  • tools/bucket_backlog.*, tools/bucket_diff.py: the new binary path and command text.
  • The HTTP user agent is al-runner/<version>.

Kept on purpose

  • The crate name alrunner-cli, so cargo build -p alrunner-cli still works.
  • The ALRUNNER_* environment variables. The owner has not decided about them.
  • The cache folders, the Windows install folder %LOCALAPPDATA%\alrunner\bin (a PATH entry from an earlier alpha keeps working), and file names such as docs/adr/028-alrunner-serve.md and docs/alrunner-buckets.md.
  • Older ADRs, docs/owner-review.md, docs/reviews/ and docs/probes-needed.md keep the old name as written. ADR-016 has a new section on the rename and the note.
  • README.md is not changed here. A separate PR rewrites the README with the new name.

Tests

  • Red, then green: 8 cases in crates/alrunner-cli/tests/cli.rs (fake al-runner scripts on a test PATH: the note, once a day, the off switch, ~/.dotnet/tools, self and shim skipped, the --version list, the 2-second limit, a closed pipe), 3 in the new tests/install_script.rs (installs from a local release folder), and 2 unit tests in path_note.rs.
  • check.sh: green.
  • Full corpus run with --baseline-diff: 0 baseline cases lost on every lane.
  • corpus_resolve_deps -- --ignored: 4 of 4 pass.

Not done

  • install.ps1 is parse-checked only. I could not run it on Windows.
  • No crate rename.

https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ

The binary alrunner becomes al-runner (ADR-016, owner decision 2026-10-21):
the Cargo bin name, the --version line ("al-runner 3.x (commit)"), the
release archives al-runner-<label>-<target>, the release-tag version check,
release/smoke.sh, the installers, tools/bucket_backlog and the help and docs.
Kept: the crate name alrunner-cli, the ALRUNNER_* variables, the cache folders,
the Windows install folder %LOCALAPPDATA%\alrunner\bin and file names such as
028-alrunner-serve.md. Older ADRs and history keep the old name as written.

AL Runner v2's dotnet tool is also called al-runner. Every command except
serve, --help and --version now prints one stderr line when another al-runner
is on PATH or in ~/.dotnet/tools, at most once a day. --version lists the other
copies with the first line of their --version (2 s limit each).
ALRUNNER_NO_PATH_NOTE=1 turns both off. The installers point out v2, the PATH
order, and a leftover alrunner, and still install a release from before the
rename under its old name.

Claude-Session: https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ
…n error

The list of other al-runner copies comes after the version line. A tool that
reads only that line (al-runner --version | head -1) closed the pipe before
the list, and println! panicked. The list now stops on a write error.

Claude-Session: https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ
…runner

# Conflicts:
#	.github/workflows/release-tag.yml
#	docs/agents/remote-worker.md
@StefanMaron
StefanMaron enabled auto-merge October 21, 2026 06:26
@StefanMaron
StefanMaron merged commit 9de1d7f into main Oct 21, 2026
7 checks passed
@StefanMaron
StefanMaron deleted the binary-al-runner branch October 21, 2026 06:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant