Skip to content

v4.1
Compare
Choose a tag to compare
@freddydk freddydk released this 22 Jan 12:58
· 52 commits to main since this release
v4.1
ad7ba19
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

New Settings

  • templateSha: The SHA of the version of AL-Go currently used

New Actions

  • DumpWorkflowInfo: Dump information about running workflow
  • Troubleshooting : Run troubleshooting for repository

Update AL-Go System Files

Add another parameter when running Update AL-Go System Files, called downloadLatest, used to indicate whether to download latest version from template repository. Default value is true.
If false, the templateSha repository setting is used to download specific AL-Go System Files when calculating new files.

Issues

  • Issue 782 Exclude '.altestrunner/' from template .gitignore
  • Issue 823 Dependencies from prior build jobs are not included when using useProjectDependencies
  • App artifacts for version 'latest' are now fetched from the latest CICD run that completed and successfully built all the projects for the corresponding branch.
  • Issue 824 Utilize useCompilerFolder setting when creating an development environment for an AL-Go project.
  • Issue 828 and 825 display warnings for secrets, which might cause AL-Go for GitHub to malfunction

New Settings

  • alDoc : JSON object with properties for the ALDoc reference document generation
    • continuousDeployment = Determines if reference documentation will be deployed continuously as part of CI/CD. You can run the Deploy Reference Documentation workflow to deploy manually or on a schedule. (Default false)
    • deployToGitHubPages = Determines whether or not the reference documentation site should be deployed to GitHub Pages for the repository. In order to deploy to GitHub Pages, GitHub Pages must be enabled and set to GitHub Actions. (Default true)
    • maxReleases = Maximum number of releases to include in the reference documentation. (Default 3)
    • groupByProject = Determines whether projects in multi-project repositories are used as folders in reference documentation
    • includeProjects = An array of projects to include in the reference documentation. (Default all)
    • excludeProjects = An array of projects to exclude in the reference documentation. (Default none)-
    • header = Header for the documentation site. (Default: Documentation for...)
    • footer = Footer for the documentation site. (Default: Made with...)
    • defaultIndexMD = Markdown for the landing page of the documentation site. (Default: Reference documentation...)
    • defaultReleaseMD = Markdown for the landing page of the release sites. (Default: Release reference documentation...)
    • Note that in header, footer, defaultIndexMD and defaultReleaseMD you can use the following placeholders: {REPOSITORY}, {VERSION}, {INDEXTEMPLATERELATIVEPATH}, {RELEASENOTES}

New Workflows

  • Deploy Reference Documentation is a workflow, which you can invoke manually or on a schedule to generate and deploy reference documentation using the aldoc tool, using the ALDoc setting properties described above.
  • Troubleshooting is a workflow, which you can invoke manually to run troubleshooting on the repository and check for settings or secrets, containing illegal values. When creating issues on https://github.com/microsoft/AL-Go/issues, we might ask you to run the troubleshooter to help identify common problems.

Support for ALDoc reference documentation tool

ALDoc reference documentation tool is now supported for generating and deploying reference documentation for your projects either continuously or manually/scheduled.

Assets 2