BC Observatoryunofficial, made by waldo
code change · fixAL Developmentofficial - Microsoftreviewed - checked by Opus

#2300 Make failOn: newWarning work with workspace compilation

The failOn: newWarning setting now detects newly introduced AL compiler warnings when workspace compilation is enabled, by running the check during the compile phase instead of the pipeline phase and handling workspace-format compiler output.

Open in Claude2300.mdPull request #2300

Pull request · merged into main on 2026-07-31 by aholstrup1 · 5 files (+283 -20), 3 AL · fix · tier official · reviewed (checked by Opus)

What changed

  • The newWarning check now runs in the CompileApps action when workspace compilation is on, and RunPipeline skips it in that mode
  • CheckForWarningsUtils.psm1 moved to Actions/.Modules so both actions can use it
  • Parser now reads both GitHub annotation format and raw AL compiler output
  • Four-part version numbers in warning text are normalized so build-number changes do not cause false new warnings
  • RunPipeline passes an empty buildOutputFile to Run-AlPipeline so the compiler output is kept for the baseline artifact
  • Behaviour changes for users or extensions.

AL objects touched

  • Actions/.Modules/CheckForWarningsUtils.psm1: renamed, not in the BC? snapshot
  • Actions/CompileApps/Compile.ps1: modified, not in the BC? snapshot
  • Actions/RunPipeline/RunPipeline.ps1: modified, not in the BC? snapshot

Context

  • Systems: development, platform

Source: metadata of a merged pull request in microsoft/AL-Go (al-go): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).