This repository was archived by the owner on Oct 21, 2026. It is now read-only.
Repository navigation
Rename the binary to al-runner and note AL Runner v2 on PATH - #395
Merged
Merged
Conversation
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
# Conflicts: # docs/owner-review.md
StefanMaron
enabled auto-merge
October 21, 2026 06:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The binary
alrunnerbecomesal-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
[[bin]] name = "al-runner"incrates/alrunner-cli/Cargo.toml.--versionprintsal-runner 3.x (commit). Help text, error texts,CARGO_BIN_EXE_al-runnerin the tests, and docs use the new name.build-packages.ymlbuilds archives namedal-runner-<label>-<target>.release-tag.ymlchecks that--versionstarts withal-runner $VERSION.release/smoke.shand the release titles match.install.shandinstall.ps1installal-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 oldalrunnersits in the install folder, and when AL Runner v2 is in~/.dotnet/tools. If v2's folder comes first onPATH, they say which order to use.al-runneron PATH (crates/alrunner-cli/src/path_note.rs). Every command exceptserve,--helpand--versionlooks for otheral-runnerfiles onPATHand 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.--versionlists 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=1turns the note and the list off.tools/bucket_backlog.*,tools/bucket_diff.py: the new binary path and command text.al-runner/<version>.Kept on purpose
alrunner-cli, socargo build -p alrunner-clistill works.ALRUNNER_*environment variables. The owner has not decided about them.%LOCALAPPDATA%\alrunner\bin(aPATHentry from an earlier alpha keeps working), and file names such asdocs/adr/028-alrunner-serve.mdanddocs/alrunner-buckets.md.docs/owner-review.md,docs/reviews/anddocs/probes-needed.mdkeep the old name as written. ADR-016 has a new section on the rename and the note.README.mdis not changed here. A separate PR rewrites the README with the new name.Tests
crates/alrunner-cli/tests/cli.rs(fakeal-runnerscripts on a testPATH: the note, once a day, the off switch,~/.dotnet/tools, self and shim skipped, the--versionlist, the 2-second limit, a closed pipe), 3 in the newtests/install_script.rs(installs from a local release folder), and 2 unit tests inpath_note.rs.check.sh: green.--baseline-diff: 0 baseline cases lost on every lane.corpus_resolve_deps -- --ignored: 4 of 4 pass.Not done
install.ps1is parse-checked only. I could not run it on Windows.https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ