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
+34-1Lines changed: 34 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,36 @@
1
+
## v6.1
2
+
3
+
### Issues
4
+
5
+
- Issue 1241 Increment Version Number might produce wrong app.json
6
+
- When auto discovering appFolders, testFolders and bcptTestFolders - if a BCPT Test app has a dependency to a test framework app, it is added to testFolders as well as bcptTestFolders and will cause a failure.
7
+
8
+
### New Project Settings
9
+
10
+
-`pageScriptingTests` should be an array of page scripting test file specifications, relative to the AL-Go project. Examples of file specifications: `recordings/my*.yml` (for all yaml files in the recordings subfolder matching my\*.yml), `recordings` (for all \*.yml files in the recordings subfolder) or `recordings/test.yml` (for a single yml file)
11
+
-`doNotRunPageScriptingTests` can force the pipeline to NOT run the page scripting tests specified in pageScriptingTests. Note this setting can be set in a [workflow specific settings file](#where-are-the-settings-located) to only apply to that workflow
12
+
-`restoreDatabases` should be an array of events, indicating when you want to start with clean databases in the container. Possible events are: `BeforeBcpTests`, `BeforePageScriptingTests`, `BeforeEachTestApp`, `BeforeEachBcptTestApp`, `BeforeEachPageScriptingTest`
13
+
14
+
### New Repository Settings
15
+
16
+
-`trustedSigning` is a structure defining `Account`, `EndPoint` and `CertificateProfile` if you want to use trusted signing. Note that your Azure_Credentials secret (Microsoft Entra ID App or Managed identity) still needs to provide access to your azure subscription and be assigned the `Trusted Signing Certificate Profile Signer` role in the Trusted Signing Account.
17
+
-`deployTo<environment>` now has an additional property called DependencyInstallMode, which determines how dependencies are deployed if GenerateDependencyArtifact is true. Default value is `install` to install dependencies if not already installed. Other values are `ignore` for ignoring dependencies, `upgrade` for upgrading dependencies if possible and `forceUpgrade` for force upgrading dependencies.
18
+
19
+
### Support for Azure Trusted Signing
20
+
21
+
Read https://learn.microsoft.com/en-us/azure/trusted-signing/ for more information about Trusted Signing and how to set it up. After setting up your trusted signing account and certificate profile, you need to create a setting called [trustedSigning](https://aka.ms/algosettings#trustedSigning) for AL-Go to sign your apps using Azure Trusted Signing.
22
+
23
+
### Support for Page Scripting Tests
24
+
25
+
Page Scripting tests are now supported as part of CI/CD. By specifying pageScriptingTests in your project settings file, AL-Go for GitHub will automatically run these page scripting tests as part of your CI/CD workflow, generating the following build artifacts:
26
+
27
+
-`PageScriptingTestResults` is a JUnit test results file with all results combined.
28
+
-`PageScriptingTestResultDetails` are the detailed test results (including videos) when any of the page scripting tests have failures. If the page scripting tests succeed - the details are not published.
29
+
30
+
### Experimental support for Git submodule
31
+
32
+
[Git submodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) is now supported as part of CI/CD on your project.
33
+
1
34
## v6.0
2
35
3
36
### Issues
@@ -648,7 +681,7 @@ Setting the repo setting "runs-on" to "Ubuntu-Latest", followed by running Updat
648
681
### CI/CD and Publish To New Environment
649
682
650
683
- Base functionality for selecting a specific GitHub runner for an environment
651
-
- Include dependencies artifacts when deploying (if generateDependencyArtifacts is true)
684
+
- Include dependencies artifacts when deploying (if generateDependencyArtifact is true)
0 commit comments