---
id: change/al-go/2300
type: change
title: "#2300 Make failOn: newWarning work with workspace compilation"
summary: "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."
tier: official
language: en
tags:
  - fix
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:10:53.023Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 838fe7b9ea8ea5e0a41843d115390ac5da4732ef
evidence:
  - kind: code
    url: https://github.com/microsoft/AL-Go/pull/2300
    title: "microsoft/AL-Go#2300: Make failOn: newWarning work with workspace compilation"
    date: "2026-07-31"
    commit: 838fe7b9ea8ea5e0a41843d115390ac5da4732ef
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 2300
repo: microsoft/AL-Go
source_id: al-go-prs
url: https://github.com/microsoft/AL-Go/pull/2300
kind: pr
base_branch: main
major: null
merged_at: "2026-07-31T07:30:39Z"
author: aholstrup1
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: fix
behavior_change: true
breaking: false
files:
  count: 5
  additions: 283
  deletions: 20
  al: 3
apps: []
objects_touched: []
objects_unjoined:
  - path: Actions/.Modules/CheckForWarningsUtils.psm1
    status: renamed
    reason: not-in-snapshot
  - path: Actions/CompileApps/Compile.ps1
    status: modified
    reason: not-in-snapshot
  - path: Actions/RunPipeline/RunPipeline.ps1
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - development
  - platform
quote: null
joined_against:
  major: null
  commit: null
---

# #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.

[Pull request](https://github.com/microsoft/AL-Go/pull/2300) · 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).