#2342 Fix incremental builds poisoning buildMode-specific artifacts (#2337)
Fixed incremental builds in AL-Go that were corrupting buildMode-specific artifacts by re-publishing default build mode apps under incorrect artifact names, causing dependent projects to fail with runtime version mismatches.
- 7files
- 5AL files
- 0objects
Pull request · merged into main on 2026-08-07 by aholstrup1 · 7 files (+152 -6), 5 AL · fix · tier official · reviewed (checked by Opus)
What changed
- DetermineBuildProject now receives buildMode parameter to download artifacts matching the current build mode dimension
- Build-mode-prefixed artifact masks are used instead of build-mode-agnostic masks to select correct artifacts
- Downloaded artifacts are extracted into build-mode-agnostic folders for later build steps, maintaining compatibility
- Fixes propagating corruption in incremental builds where each run becomes the baseline for the next
- Prevents AL1153 compiler errors from runtime version mismatches in multi-project repositories
- Behaviour changes for users or extensions.
AL objects touched
Actions/DetermineBuildProject/DetermineBuildProject.ps1: modified, not in the BC? snapshotActions/DetermineBuildProject/README.md: modified, not in the BC? snapshotActions/DetermineBuildProject/action.yaml: modified, not in the BC? snapshotTemplates/AppSource App/.github/workflows/_BuildALGoProject.yaml: modified, not in the BC? snapshotTemplates/Per Tenant Extension/.github/workflows/_BuildALGoProject.yaml: modified, not in the BC? snapshot
Context
- Systems: platform, development
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).