[releases/26.x@20e51de] Update AL-Go System Files from microsoft/AL-Go-PTE@preview - 041d3b7 / Related to AB#539394

[business-central-bot]

v8.0

Mechanism to overwrite complex settings type

By default, AL-Go merges settings from various places (see settings levels). Basic setting types such as string and integer are overwritten, but settings with complex types such as array and object are merged.

However, sometimes it is useful to avoid merging complex types. This can be achieved by specifying overwriteSettings property on a settings object. The purpose of the property is to list settings, for which the value will be overwritten, instead of merged. Read more at overwriteSettings property

AL Code Analysis tracked in GitHub

AL-Go already supports AL code analysis, but up until now this was not tracked in GitHub. It is now possible to track code analysis issues automatically in the GitHub security tab, as well as having any new issues posted as a comment in Pull Requests.

Enable this feature by using the new setting trackALAlertsInGithub. This setting must be enabled at the repo level, but can optionally be disabled per project.

Please note that some automated features are premium and require the use of GitHub Code Security

Issues

• Discussion 1885 Conditional settings for CI/CD are not applied
• Discussion 1899 Remove optional properties from "required" list in settings.schema.json
• Issue 1905 AL-Go system files update fails (Get Workflow Multi-Run Branches action fails when there are tags with same value but different casing)
• Issue 1926 Deployment fails when using build modes
• Issue 1898 GetDependencies in localDevEnv does not fallback to github token
• Issue 1947 Project settings are ignored when loading bccontainerhelper
• Issue 1937 trackALAlertsInGitHub is failing in preview
• DeployTo settings from environment-specific AL-Go settings are not applied when deploying
• ReadSettings action outputs too much information that is mainly used for debugging

Related to AB#539394