Repository navigation
AL-Go Telemetry Enhancements
AL-Go now includes RepositoryIsFork and GitHubHostingType in Microsoft and partner telemetry. These identify whether the workflow repository is a fork and whether it runs on GitHub.com, GitHub Enterprise Cloud with data residency (*.ghe.com), or GitHub Enterprise Server. GitHub.com includes Enterprise Cloud customers hosted there; this classification does not identify subscription plans or send server hostnames. Unavailable metadata is reported as Unknown.
Action telemetry now includes structured ActionName and ActionConclusion dimensions. The action wrapper reports Success or Failure, allowing consumers to group action outcomes without parsing message text. Handled error events do not independently mark the action as failed.
Allow pre-release packages as NuGet dependencies
AL-Go now supports including pre-release versions of Business Central app packages from NuGet feeds. To enable this, append -allowPrerelease to the nuGetFeedSelectMode setting in your project configuration. For example, LatestMatching-allowPrerelease will select the latest matching version of the package, including pre-release versions.
New unpublishOldVersions setting for deployment
The DeployTo<environment> setting now supports an opt-in unpublishOldVersions boolean (default false). When enabled, AL-Go unpublishes old, uninstalled versions of the deployed apps from the environment after a successful deployment, keeping Extension Management clean. This only applies to PTE deployments (Scope PTE / automation API), uses the Automation API v2.0 Microsoft.NAV.unpublish action, and is non-fatal (failures are reported as warnings and never fail the deployment).
Expanded AL-Go telemetry dashboard
The starter Azure Data Explorer dashboard now includes dedicated views for workflow reliability, run exploration, test quality, workflow duration, runner efficiency, and AL-Go maintenance. It also provides repository, workflow, branch, and repository-type filtering, clearer empty states, and repository-level runtime supportability information.
Create Release checks AL-Go system file updates separately
The Create Release workflow now checks for available AL-Go system file updates in a separate job that runs in parallel with and independently of release creation. This allows the release to be created without waiting for the update check and can reduce the overall workflow duration.
Local development environments use cacheImageName
localDevEnv now passes the configured cacheImageName to Run-AlPipeline, allowing BcContainerHelper to reuse artifact-specific images.
To retain the previous behavior, set cacheImageName to an empty string in .AL-Go/localDevEnv.settings.json.
Issues
- Workflow finalization telemetry failures, including GitHub API errors, no longer fail an otherwise successful workflow.
- Issue 2358 - Update AL-Go System Files no longer creates a commit or pull request when only the template SHA would change, avoiding unnecessary CI/CD runs.
- Issue 2370 - Retry CI/CD baseline discovery when no eligible run is returned, logging result counts for diagnostics and URL-encoding query values so discovery URLs render correctly in logs. The existing full-build fallback is preserved when no baseline is found after retries.
- Issue 2113 - Fix device-login initialization in Create Online Dev. Environment and Publish To Environment when authentication secrets are unavailable.
- Issue 2375 - Project/App folder with umlaut breaks incremental build check
- Issue 2381 - Dependency artifacts from the current build are not downloaded when the branch name contains glob-special characters (e.g.
,), silently falling back to baseline artifacts - Issue 2389 - URLs in localdevenv and the settings schema are wrong when running a self-hosted AL-Go from a fork