You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/RELEASENOTES.copy.md
+138-2Lines changed: 138 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,134 @@
2
2
3
3
Note that when using the preview version of AL-Go for GitHub, we recommend you Update your AL-Go system files, as soon as possible when informed that an update is available.
4
4
5
+
### Issues
6
+
7
+
- Issue 1915 CICD fails on releases/26.x branch - '26.x' cannot be recognized as a semantic version string
8
+
9
+
### The default pull request trigger is changing
10
+
11
+
AL-Go for GitHub is transitioning from the pull_request_target trigger to the more secure pull_request trigger. This is a step we are taking to make AL-Go for GitHub more secure by default. If you are used to working from branches within the repository you may not notice any difference. If you get pull requests from forks, those pull requests will no longer be able to access secrets. If that is blocking for your repository, you will need to update your settings to use the pull_request_target trigger.
12
+
13
+
**How do I revert back to pull_request_target?**
14
+
15
+
Add the following setting to one of your settings files and run the Update AL-Go System Files workflow:
16
+
17
+
```json
18
+
"pullRequestTrigger": "pull_request_target"
19
+
```
20
+
21
+
## v8.2
22
+
23
+
### Issues
24
+
25
+
- Issue 2095 DeliverToAppSource.ProductId needs to be specified (Library app)
26
+
- Issue 2082 Sign action no longer fails when repository is empty or no artifacts are generated
27
+
- Issue 2078 Workflows run since January 14th '26 have space before CI/CD removed
28
+
- Issue 2070 Support public GitHub Packages feeds without requiring a Personal Access Token (PAT)
29
+
- Issue 2004 PublishToAppSource workflow publishes multi-app repos in alphabetical order instead of dependency order
30
+
- Issue 2045 DateTime parsing fails on non-US locale runners in WorkflowPostProcess.ps1
31
+
- Issue 2055 When using versioningStrategy 3+16, you get an error when building
- AL-Go repositories with large amounts of projects may run into issues with too large environment variables
34
+
- Discussion 1855 Add trigger 'workflow_call' to workflow 'Update AL-Go System Files' for reusability
35
+
- Issue 2050 Publish To Environment creates mistyped environment
36
+
37
+
### Publish To Environment no longer creates unknown environments by default
38
+
39
+
Previously, when running the "Publish To Environment" workflow with an environment name that doesn't exist in GitHub or AL-Go settings, the workflow would automatically create a new GitHub environment. This could lead to problems when environment names were mistyped, as the bogus environment would then cause subsequent CI/CD workflows to fail.
40
+
41
+
Now, the workflow will fail with a clear error message if the specified environment doesn't exist. If you intentionally want to deploy to a new environment that hasn't been configured yet, you can check the **Create environment if it does not exist** checkbox when running the workflow.
42
+
43
+
### Set default values for workflow inputs
44
+
45
+
The `workflowDefaultInputs` setting now also applies to `workflow_call` inputs when an input with the same name exists for `workflow_dispatch`.
46
+
This ensures consistent default values across both manual workflow runs and reusable workflow calls.
47
+
48
+
Read more at [workflowDefaultInputs](https://aka.ms/algosettings#workflowDefaultInputs).
49
+
50
+
### Merge queue support
51
+
52
+
AL-Go now supports GitHub's merge queue feature out of the box! The `merge_group` trigger has been added to the Pull Request Build workflow, enabling seamless integration with merge queues. When you have the merge queue feature enabled in your repo, multiple PRs will automatically be validated together. Read more about merge queues [here](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue).
53
+
54
+
> [!WARNING]
55
+
> If you rely on a custom workflow for merge queue validation, you may need to adjust your setup to avoid duplicate builds.
56
+
57
+
### AL-Go Telemetry updates
58
+
59
+
AL-Go telemetry now includes test results so you can more easily see how many AL tests, Page Scripting tests and BCPT tests ran in your workflows across all your repositories. Documentation for this can be found on [this article](https://github.com/microsoft/AL-Go/blob/main/Scenarios/EnablingTelemetry.md) on enabling telemetry.
60
+
61
+
## v8.1
62
+
63
+
### Custom AL-Go files
64
+
65
+
AL-Go for GitHub now supports updating files from your custom templates via the new `customALGoFiles` setting. Read more at [customALGoFiles](https://aka.ms/algosettings#customALGoFiles).
66
+
67
+
### Set default values for workflow inputs
68
+
69
+
A new setting `workflowDefaultInputs` allows you to configure default values for workflow_dispatch inputs. This makes it easier to run workflows manually with consistent settings across your team.
70
+
71
+
When you add this setting to your AL-Go settings file and run the "Update AL-Go System Files" workflow, the default values will be automatically applied to the workflow YAML files in your repository.
72
+
The default values must match the input types (boolean, number, string, or choice) defined in the workflow YAML files.
73
+
74
+
Example configuration:
75
+
76
+
```json
77
+
{
78
+
"workflowDefaultInputs": [
79
+
{ "name": "directCommit", "value": true },
80
+
{ "name": "useGhTokenWorkflow", "value": true }
81
+
]
82
+
}
83
+
```
84
+
85
+
This setting can be used on its own in repository settings to apply defaults to all workflows with matching input names. Alternatively, you can use it within [conditional settings](https://aka.ms/algosettings#conditional-settings) to apply defaults only to specific workflows, branches, or other conditions.
86
+
87
+
Example using conditional settings to target specific workflows:
88
+
89
+
```json
90
+
{
91
+
"conditionalSettings": [
92
+
{
93
+
"workflows": ["Create Release"],
94
+
"settings": {
95
+
"workflowDefaultInputs": [
96
+
{ "name": "directCommit", "value": true },
97
+
{ "name": "releaseType", "value": "Prerelease" }
98
+
]
99
+
}
100
+
}
101
+
]
102
+
}
103
+
```
104
+
105
+
**Important:** When multiple conditional settings blocks match and both define `workflowDefaultInputs`, the arrays are merged following AL-Go's standard behavior for complex setting types (all entries are kept). If the same input name appears in multiple entries, the last matching entry takes precedence.
106
+
107
+
Read more at [workflowDefaultInputs](https://aka.ms/algosettings#workflowDefaultInputs).
108
+
109
+
### Issues
110
+
111
+
- Issue 2039 Error when deploy to environment: NewTemporaryFolder is not recognized
112
+
- Issue 1961 KeyVault access in PR pipeline
113
+
- Discussion 1911 Add support for reportSuppressedDiagnostics
114
+
- Discussion 1968 Parameter for settings passed to CreateDevEnv
115
+
- Issue 1945 Deploy Reference Documentation fails for CI/CD
116
+
- Use Runner_Temp instead of GetTempFolder whenever possible
117
+
- Issue 2016 Running Update AL-Go system files with branches wildcard `*` tries to update _origin_
118
+
- Issue 1960 Deploy Reference Documentation fails
119
+
- Discussion 1952 Set default values on workflow_dispatch input
120
+
121
+
### Deprecations
122
+
123
+
-`unusedALGoSystemFiles` will be removed after October 1st 2026. Please use [`customALGoFiles.filesToExclude`](https://aka.ms/algosettings#customALGoFiles) instead.
124
+
125
+
## v8.0
126
+
127
+
### Mechanism to overwrite complex settings type
128
+
129
+
By default, AL-Go merges settings from various places (see [settings levels](https://aka.ms/algosettings#where-are-the-settings-located)). Basic setting types such as `string` and `integer` are overwritten, but settings with complex types such as `array` and `object` are merged.
130
+
131
+
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](https://aka.ms/algosettings#overwriteSettings)
132
+
5
133
### AL Code Analysis tracked in GitHub
6
134
7
135
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.
@@ -13,6 +141,14 @@ Please note that some automated features are premium and require the use of [Git
13
141
### Issues
14
142
15
143
- Discussion 1885 Conditional settings for CI/CD are not applied
144
+
- Discussion 1899 Remove optional properties from "required" list in settings.schema.json
145
+
- 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)
146
+
- Issue 1926 Deployment fails when using build modes
147
+
- Issue 1898 GetDependencies in localDevEnv does not fallback to github token
148
+
- Issue 1947 Project settings are ignored when loading bccontainerhelper
149
+
- Issue 1937 trackALAlertsInGitHub is failing in preview
150
+
- DeployTo settings from environment-specific AL-Go settings are not applied when deploying
151
+
-`ReadSettings` action outputs too much information that is mainly used for debugging
16
152
17
153
## v7.3
18
154
@@ -35,7 +171,7 @@ Example
35
171
36
172
AL-Go now offers a dataexplorer dashboard to get started with AL-Go telemetry. Additionally, we've updated the documentation to include a couple of kusto queries if you would rather build your own reports.
37
173
38
-
### Support for AL-Go settings as GitHub environment variable: ALGoEnvSettings
174
+
### Support for AL-Go settings as GitHub environment variable: ALGoEnvironmentSettings
39
175
40
176
AL-Go settings can now be defined in GitHub environment variables. To use this feature, create a new variable under your GitHub environment called `ALGoEnvironmentSettings`. Please note that this variable should not include your environment name.
41
177
@@ -905,7 +1041,7 @@ Setting the repo setting "runs-on" to "Ubuntu-latest", followed by running Updat
905
1041
### Issues
906
1042
907
1043
- Issue #143 Commit Message for **Increment Version Number** workflow
908
-
- Issue #160 Create local DevEnv aith appDependencyProbingPaths
1044
+
- Issue #160 Create local DevEnv with appDependencyProbingPaths
909
1045
- Issue #156 Versioningstrategy 2 doesn't use 24h format
0 commit comments