#2355 Move CreateRelease update check to separate job
The AL-Go CreateRelease workflow now runs update checks in a separate, parallel job instead of blocking release creation, allowing faster releases while keeping the check non-blocking.
- 5files
- 2AL files
- 0objects
Pull request · merged into main on 2026-09-18 by frottke · 5 files (+145 -24), 2 AL · refactor · tier official · reviewed (checked by Opus)
What changed
- Update check moved from CreateRelease job to dedicated CheckForUpdates job
- Both AppSource App and Per Tenant Extension templates updated
- CheckForUpdates runs in parallel with CreateRelease, no longer blocking release creation
- Check remains reporting-only with updates still applied via Update AL-Go System Files workflow
- Added test coverage for ModifyRunsOnAndShell logic with multiple job scenarios
- Behaviour changes for users or extensions.
AL objects touched
Templates/AppSource App/.github/workflows/CreateRelease.yaml: modified, not in the BC? snapshotTemplates/Per Tenant Extension/.github/workflows/CreateRelease.yaml: modified, not in the BC? snapshot
Context
- Systems: 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).