AL-Go

AL Runner shipped ~85 PRs closing correctness gaps and hardening the pipeline, bc-code-atlas's global_id now lets a self-hosted instance bridge into the public one to follow calls into Microsoft's base app, the AL Language Tests suite grew by answering AL Runner's own open questions, and the Linux fast lane got a week of real-world hardening.

The web client now works — click-through Business Central development, not just API calls, on Linux or Mac with one command. Plus cold boot down from 209s to 79s, a real production test run at 1,067 tests in 69 seconds, and BC 29 support.

If your unit tests don't touch the base application, you shouldn't have to carry it. Sub-extensions make that possible — and the performance difference is not subtle.

The definitive guide to starting a Business Central AL project right — AL-Go templates, app.json settings, naming conventions, LinterCop, and CI pipeline

Part 2 of building a NuGet installer for Business Central: version selection, NavxManifest parsing, the NAVX proprietary format mystery, and dependency

Building a Business Central extension that queries the NuGet v3 API, downloads app packages from AppSource or private feeds, and installs them using

Step-by-step AL-Go repository setup from template to first release: settings.json, shared rulesets, LinterCop, environment deployment, and org-level

Fix the FilterPageBuilder.GetView language bug by using field IDs, and integrate Spare Brained Licensing into an AppSource AL extension with AL-Go CI

How to set up a Business Central AL-Go build agent by running Windows 11 in a KVM/QEMU VM on Debian 12 — bypassing TPM requirements and cutting overhead.

Use a Git pre-commit hook with a PowerShell script to block commits with invalid app.json version numbers in Business Central AL projects — shareable