This repository was archived by the owner on Oct 21, 2026. It is now read-only.
Repository navigation
README: take over the AL Runner v2 overview, name the binary al-runner - #391
Merged
Merged
Conversation
- New title BusinessCentral.AL.Runner and the v2 one-line summary (without the "milliseconds" claim, which is not measured for v3). - Note that v3 replaces v2: v2 frozen on the v2 branch, the dotnet tool stays on NuGet, link to the tool migration guide, and that issue and PR numbers below about 5570 refer to the old StefanMaron/al-runtime-rs repository. - "What it is": v2's description (standalone test runner, a quick check before the full BC pipeline, not a replacement) rewritten for v3. - A short section on the two al-runner commands when the v2 dotnet tool is installed too. - The command name is al-runner throughout. Install folder, ALRUNNER_* variables and file names are unchanged. - License: v2 on the v2 branch stays MIT. Install, versions, usage, flags, dependencies, trust and building are unchanged. Claude-Session: https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ
…ATH paragraph and the parity doc Claude-Session: https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ
…older default and the PATH note variable serve runs all requests in one process and keeps the last compile; the README still said one child process per request. The rule that picks the BC build without --bc-version also takes the build of Microsoft's own tests and packages from --dep and --package-cache, and the target major comes from app.json. Found in a docs-vs-behavior audit of the binary. Claude-Session: https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ
StefanMaron
enabled auto-merge
October 21, 2026 06:58
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.
I merged the overview parts of the v2 README into the v3 README. Install, versions (edge and alpha), usage, flags, dependencies, trust and refusals, and building stay as they were. Only the names changed.
Merge order: first the pull request that points references at the aldevtools organization (branch
move-references), then the pull request that renames the binary to al-runner (branchbinary-al-runner), then this one. This branch is based onmove-references. The README text about the v2 tool note andal-runner --versiondescribes code that the rename pull request ships.What I took from v2 (current README on the
v2branch, plus the April version, which had more description):v2branch stays under MIT.What I left out, because it is not true for v3:
--precompile,--test-datawithbcbak, the v2 flag table and exit codes, v2 cache paths.docs/status.md.New at the top:
v2branch, the dotnet tool stays on NuGet, a link todocs/integrations/migrating-tools-to-v3.md, and that issue and pull request numbers below about 5570 refer to the oldStefanMaron/al-runtime-rsrepository.al-runnercommands when the v2 dotnet tool is also installed, with the uninstall command.The command name is
al-runnerthroughout. I did not change the Windows install folder (%LOCALAPPDATA%\alrunner\bin), theALRUNNER_*variables ordocs/alrunner-buckets.md, because the code still uses those names.https://claude.ai/code/session_01MifNJNPViEXwK4p83TH2DQ