[releases/29.x@6bf3cc0] Update AL-Go System Files from microsoft/AL-Go-PTE@preview - 35d89f9 / Related to AB#539394

[business-central-bot]

preview

Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available.

v9.2

New doNotPerformUpgrade setting

AL-Go now supports a new doNotPerformUpgrade setting that is passed through to Run-AlPipeline. Use it to skip the upgrade phase while still running the rest of the pipeline.

Workspace compilation supports framework-dependent AL Language extensions

Workspace compilation now finds altool both in the platform-specific subfolder (compiler/extension/bin/win32 or .../linux) and directly under compiler/extension/bin, so a vsixFile using the flat (framework-dependent / marketplace) layout no longer fails with "Could not find AL tool in the compiler folder". URL-based customCodeCops are likewise downloaded to the flat bin folder when no Analyzers subfolder is present. The aldoc tool used for reference documentation is resolved the same way, falling back to the flat bin folder when no platform subfolder is present.

failOn: newWarning now works with workspace compilation

Previously, the failOn: newWarning setting (which fails a pull request when it introduces new AL compiler warnings) only took effect when compiling in a container or compiler folder. It had no effect when workspaceCompilation was enabled, because the new-warning comparison only ran in the RunPipeline action, whereas workspace compilation produces the compiler output in the CompileApps action. The check now also runs in CompileApps, so failOn: newWarning is honored with workspace compilation.

As part of this, the warning comparison now also parses the raw AL compiler output format emitted by workspace compilation (in addition to the GitHub Actions annotation format), and it ignores embedded build version numbers in warning messages so that version differences between the baseline build and the pull request build no longer produce false "new warning" failures.

Issues

• Issue 2285 - CheckForUpdates now handles settings file $schema reordering in a PowerShell 5-safe way to avoid writing invalid entries like "*": null to settings JSON files.
• Fix "filename or extension is too long" error when validating settings on PS5.1 with large settings JSON
• Fix dependency apps not being resolved when the branch name contains a ] character (the dependency folder was matched as a wildcard pattern instead of enumerated literally, resulting in 0 apps being published)
• Retry downloading dependency artifacts from the current build up to 3 times (30 seconds between attempts) to tolerate transient network errors such as "Failed to GetSignedArtifactURL: Unable to make request: ETIMEDOUT"
• Issue 2256 - Test Result Analyzer fails if no stack trace is available
• Issue 2302 - AlDoc does not use --packagecache when building reference documentation
• Reference documentation no longer fails with "InvalidTocInclude: Referenced TOC file ... does not exist" for apps whose name contains an underscore (e.g. _Exclude_* apps). The toc.yml folder names are now derived using the same rules as the aldoc tool, which keeps underscores instead of turning them into hyphens.
• Issue 2319 - Under workspace compilation, enableCodeAnalyzersOnTestApps: false now also disables custom analyzers (customCodeCops) for test apps and BCPT test apps, not just the built-in code analyzers.
• Issue 2267 - AppSourceCop.json is now created for test apps when enableCodeAnalyzersOnTestApps is true.
• Issue 2320 - Deliver to NuGet of release workflow failing with app and test app
• Issue 2337 - Incremental builds: skipped projects re-publish Default-mode apps into ALL buildMode-specific artifacts

Valid SARIF URIs for file paths containing spaces

ProcessALCodeAnalysisLogs now URI-encodes each segment of the artifact location path when writing SARIF (for example 1.Setup Data/Foo.al becomes 1.Setup%20Data/Foo.al). Paths that contain spaces or other characters that are not valid in a URI previously caused github/codeql-action/upload-sarif to log "is not a valid URI" warnings and could prevent AL code scanning alerts from mapping to the correct files. The / path separators are preserved so the path structure is unchanged.

AL alerts for the workspace compilation build

The trackALAlertsInGitHub setting now also works when workspaceCompilation (preview) is enabled. When both are turned on, AL-Go passes --errorlogdirectory to altool workspace compile so each project emits an *.errorLog.json diagnostics file into .buildartifacts/ErrorLogs/, which is processed into SARIF and surfaced as code scanning alerts — matching the classic Run-AlPipeline behavior. If the consumed compiler version does not yet support --errorlogdirectory, the option is skipped and a warning is logged (the rest of the build is unaffected).

Related to AB#539394