---
id: video/vDGrVHQHLA0
type: video
title: AL-Go for Github May Office Hour
summary: "AL-Go for GitHub May 2025 office hour: three preview items shipping with 7.2 (early input validation for create release and increment version number, a settings schema property, and failing PRs on new warnings), plus notes on BC Container Helper deprecation, AL-Go versions below 5.0 stopping, and artifact storage URLs moving to front door by end of June. Also covers Freddy leaving Microsoft, with the engineering systems team taking over, and Q&A on unsupported scenarios."
tier: official
language: en
tags:
  - al-go
  - github workflows
  - input validation
  - schema validation
  - pull request
  - warnings
  - container helper
  - version updates
  - deprecation
  - page scripting
  - cicd
  - release notes
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-07T22:56:46.089Z"
  flags: []
generated:
  at: "2026-10-07T22:56:46.145Z"
  pipeline: 0.2.0
  prompts:
    extract-video: 1
    summarize-video: 2
  input_hash: 13b5cef9a93ee756e3904c0db1b4f840559a2eb06f86dd91f4f79f3cf601d118
evidence:
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s
    title: "Input Validation for Workflows: preview"
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 247
    quote: So those were the three things we've added to ALGO in the last month. Right now it's in preview.
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=118s
    title: "AL-Go Settings Schema Property: preview"
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 118
    quote: If you're on preview, you might already see it. Otherwise, you'll have to wait for the 7.2
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s
    title: "Fail Pull Requests on New Warnings: preview"
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 247
    quote: Right now it's in preview. Uh I don't know if we have any. We'll ship 7.2 soon
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=60s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 60
    quote: we've enhanced that in the in the latest preview. Um, so now what we saw was that when you ran the create release workflow,
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=130s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 130
    quote: at the top of your ALGO file, you get this schema property. And the schema property will do two things for you. First of
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=217s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 217
    quote: So, this new feature failing pull requests on your warnings. Um, so it won't change the behavior of your CI/CD workflows. Uh, that'll still
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=266s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 266
    quote: PC container helper versions earlier than se 6.1 uh, basically don't really work anymore. Um, algo repositories are not affected
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=303s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 303
    quote: please make sure you regularly update your run update algo system files uh because some of the earlier versions of a go will soon
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=316s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 316
    quote: 5.0 and lower sorry 5.0 will work lower than 5.0 will not work. Uh for reference 5.0 is about a year old now.
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=373s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 373
    quote: I am no longer with Microsoft or I'm still here uh at least for for for some time being. Um but I'm like no
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=549s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 549
    quote: so busy container upper is not deprecated yet. It's deprecated in about two years time I believe is scheduled. um and and it is
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 788
    quote: We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement of
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 788
    quote: We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1069s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1069
    quote: this feature essentially looks at new warnings only. So if you have a codebase that already has a bunch of warnings and you want
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1086s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1086
    quote: there are other ways to control breaking and failing on warnings, but not um threshold that is configurable in terms of the number of
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1179s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1179
    quote: Azure boards integration being one of them. Uh so you can reference work items from GitHub and it creates automatically creates a link
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1304s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1304
    quote: If you look at the teams I don't think there's any doubt that GitHub receives the most love and attention from development teams. A
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1422s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1422
    quote: we haven't built support for that into a go yet. That's something that needs to be investigated and and how we can do that
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1487s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1487
    quote: guess there is a co pilot uh code review but it's not very good at al yet
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1600s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1600
    quote: On the ELGO project board, there are some cards about auto translation. Is there any news on that? I don't believe so.
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1664s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1664
    quote: the biggest feature that came out of that round table was the incremental builds feature
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1664s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1664
    quote: the biggest feature that came out of that round table was the incremental builds feature 23 that was in that was that round table
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1844s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 1844
    quote: Seems like it this this is maybe a good opportunity to also promote a little bit the discussions we have on GitHub where we
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2104s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2104
    quote: those URLs would be something like bc artifacts.blo.s storage.net or something like that. Uh and those will not work in the future.
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2143s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2143
    quote: at the end of June we'll we'll stop you know the ability to access the storage accounts directly and so by that time all
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2193s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2193
    quote: It is definitely not. we have a still have a bunch of work left to make a go independent of container helper
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2248s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2248
    quote: the modifications in ALGO will probably I mean you probably won't notice them in a lot of cases things will just happen and suddenly
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2507s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2507
    quote: we just got another person working on Algo as well, Sebastian. And, uh, yeah, even though Freddy is leaving, we will be continuing to
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2540s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2540
    quote: there is a statement from uh Dimmitri from Microsoft uh basically also stating that we're not defunding our efforts into the go
  - kind: video
    url: https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2638s
    title: AL-Go for Github May Office Hour
    date: "2025-05-27T11:19:23.000Z"
    commit: null
    t: 2638
    quote: I'm going to start my own business and figure out how I can I can manage life, work, and whatever experiences I want to
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
video_id: vDGrVHQHLA0
channel: yt-microsoft
source_name: Microsoft Dynamics 365 Business Central (YouTube)
url: https://www.youtube.com/watch?v=vDGrVHQHLA0
published_at: "2025-05-27T11:19:23.000Z"
duration_s: 2978
captions: full
audience:
  - developer
  - administrator
  - functional consultant
chapters:
  - t: 0
    title: Input Validation and Create Release Enhancements
  - t: 101
    title: AL-Go Settings Schema and Validation
  - t: 190
    title: Failing Pull Requests on New Warnings
  - t: 247
    title: "Announcements: Container Helper and Version Updates"
  - t: 326
    title: Freddy's Departure and Team Transition
  - t: 470
    title: Team Composition and Pull Request Warning Settings
  - t: 549
    title: BC Container Helper Deprecation and Future Plans
  - t: 668
    title: AL-Go Future Investment and Building Artifacts
  - t: 788
    title: Page Scripting and Community Events
  - t: 896
    title: AL-Go Onboarding, Community Engagement, and Artifact Storage
  - t: 1048
    title: Warning Thresholds and Azure DevOps Integration
  - t: 1195
    title: Migration Strategy Between Azure DevOps and GitHub
  - t: 1347
    title: Data-Driven Testing, Copilot Code Review, and Runtime Packages
  - t: 1571
    title: Auto Translation and Incremental Builds Discussion
  - t: 1703
    title: Feature Requests and GitHub Discussions for Backlog
  - t: 1894
    title: GitHub Organization and Enterprise Licensing Structure
  - t: 1959
    title: AL-Go Documentation Gaps and Enterprise Licensing Questions
  - t: 2042
    title: Artifact URL Changes and BC Container Helper Deprecation
  - t: 2227
    title: AL-Go Independence and Security Updates
  - t: 2358
    title: Translation Feature Request and Resource Allocation
  - t: 2560
    title: Commitment to Community and Freddy's Future Plans
  - t: 2676
    title: Management Transition and Team Structure
  - t: 2758
    title: Closing Remarks and Logistics
features:
  - name: Input Validation for Workflows
    status: preview
    t: 60
    verified: true
    status_source: video
  - name: AL-Go Settings Schema Property
    status: preview
    t: 118
    verified: true
    status_source: video
  - name: Fail Pull Requests on New Warnings
    status: preview
    t: 190
    verified: true
    status_source: video
  - name: BC Container Helper Deprecation Notice
    status: unclear
    t: 266
    verified: false
    status_source: video
  - name: Page Scripting Tests on SaaS Environments
    status: unclear
    t: 775
    verified: false
    status_source: video
  - name: Azure DevOps and GitHub Integration
    status: unclear
    t: 1154
    verified: false
    status_source: video
  - name: Data-Driven Testing Support
    status: unclear
    t: 1372
    verified: false
    status_source: video
  - name: GitHub Copilot Code Review for AL
    status: unclear
    t: 1461
    verified: false
    status_source: video
  - name: Building Runtime Packages in AL-Go
    status: unclear
    t: 1553
    verified: false
    status_source: video
  - name: Auto Translation Feature
    status: unclear
    t: 1600
    verified: false
    status_source: video
  - name: Incremental Builds Feature
    status: unclear
    t: 1664
    verified: false
    status_source: video
  - name: GitHub Discussions Ideas Tab
    status: unclear
    t: 1844
    verified: false
    status_source: video
  - name: Artifact URL Migration to Front Door
    status: unclear
    t: 2073
    verified: false
    status_source: video
  - name: AL-Go Independence from BC Container Helper
    status: unclear
    t: 2176
    verified: false
    status_source: video
objects_mentioned:
  - other create release workflow
  - other increment version number workflow
  - other AL-Go file
  - other AL-Go settings file
  - other Azure Boards
  - other AI test toolkit
  - other pre-commit
  - other code cut
quotes:
  - t: 60
    text: we've enhanced that in the in the latest preview. Um, so now what we saw was that when you ran the create release workflow,
    check: exact
  - t: 130
    text: at the top of your ALGO file, you get this schema property. And the schema property will do two things for you. First of
    check: exact
  - t: 217
    text: So, this new feature failing pull requests on your warnings. Um, so it won't change the behavior of your CI/CD workflows. Uh, that'll still
    check: exact
  - t: 266
    text: PC container helper versions earlier than se 6.1 uh, basically don't really work anymore. Um, algo repositories are not affected
    check: exact
  - t: 303
    text: please make sure you regularly update your run update algo system files uh because some of the earlier versions of a go will soon
    check: exact
  - t: 316
    text: 5.0 and lower sorry 5.0 will work lower than 5.0 will not work. Uh for reference 5.0 is about a year old now.
    check: exact
  - t: 373
    text: I am no longer with Microsoft or I'm still here uh at least for for for some time being. Um but I'm like no
    check: exact
  - t: 549
    text: so busy container upper is not deprecated yet. It's deprecated in about two years time I believe is scheduled. um and and it is
    check: exact
  - t: 788
    text: We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement of
    check: exact
  - t: 788
    text: We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement
    check: exact
  - t: 1069
    text: this feature essentially looks at new warnings only. So if you have a codebase that already has a bunch of warnings and you want
    check: exact
  - t: 1086
    text: there are other ways to control breaking and failing on warnings, but not um threshold that is configurable in terms of the number of
    check: exact
  - t: 1179
    text: Azure boards integration being one of them. Uh so you can reference work items from GitHub and it creates automatically creates a link
    check: exact
  - t: 1304
    text: If you look at the teams I don't think there's any doubt that GitHub receives the most love and attention from development teams. A
    check: exact
  - t: 1422
    text: we haven't built support for that into a go yet. That's something that needs to be investigated and and how we can do that
    check: exact
  - t: 1487
    text: guess there is a co pilot uh code review but it's not very good at al yet
    check: fuzzy
  - t: 1600
    text: On the ELGO project board, there are some cards about auto translation. Is there any news on that? I don't believe so.
    check: exact
  - t: 1664
    text: the biggest feature that came out of that round table was the incremental builds feature
    check: exact
  - t: 1664
    text: the biggest feature that came out of that round table was the incremental builds feature 23 that was in that was that round table
    check: exact
  - t: 1844
    text: Seems like it this this is maybe a good opportunity to also promote a little bit the discussions we have on GitHub where we
    check: exact
  - t: 2104
    text: those URLs would be something like bc artifacts.blo.s storage.net or something like that. Uh and those will not work in the future.
    check: snapped
  - t: 2143
    text: at the end of June we'll we'll stop you know the ability to access the storage accounts directly and so by that time all
    check: exact
  - t: 2193
    text: It is definitely not. we have a still have a bunch of work left to make a go independent of container helper
    check: exact
  - t: 2248
    text: the modifications in ALGO will probably I mean you probably won't notice them in a lot of cases things will just happen and suddenly
    check: exact
  - t: 2507
    text: we just got another person working on Algo as well, Sebastian. And, uh, yeah, even though Freddy is leaving, we will be continuing to
    check: exact
  - t: 2540
    text: there is a statement from uh Dimmitri from Microsoft uh basically also stating that we're not defunding our efforts into the go
    check: exact
  - t: 2638
    text: I'm going to start my own business and figure out how I can I can manage life, work, and whatever experiences I want to
    check: exact
  - t: 2714
    text: Elgo will fall under and I mean has fallen under the engineering systems team which is the team I work on Maria work on
    check: exact
  - t: 2742
    text: it's been under it's been under our team for a couple of years, but Fred has still been the one coming up with a
    check: exact
  - t: 2845
    text: you can always reach us on in the discussion tab on ALGO. There's also a questions uh tab
    check: exact
---

# AL-Go for Github May Office Hour

> AL-Go for GitHub May 2025 office hour: three preview items shipping with 7.2 (early input validation for create release and increment version number, a settings schema property, and failing PRs on new warnings), plus notes on BC Container Helper deprecation, AL-Go versions below 5.0 stopping, and artifact storage URLs moving to front door by end of June. Also covers Freddy leaving Microsoft, with the engineering systems team taking over, and Q&A on unsupported scenarios.

[Watch on YouTube](https://www.youtube.com/watch?v=vDGrVHQHLA0) · Microsoft Dynamics 365 Business Central (YouTube) · 2025-05-27 · 49:38 · tier official · reviewed (checked by Opus)

## Overview

The May 2025 AL-Go for GitHub office hour covers recent changes and announcements. Workflows for create release and increment version number now fail early on invalid inputs. A schema property in the AL-Go settings file gives VS Code suggestions and validation, and pull requests can be failed on new warnings only. Both are in preview, with 7.2 mentioned as the release to wait for.

The team also announced that BC Container Helper versions before 6.1 no longer work (AL-Go repositories are not affected), that AL-Go system file versions 5.0 and lower will stop working, and that artifact URLs move behind a front door at the end of June. The Q&A covers Azure DevOps and GitHub integration, data-driven testing, Copilot code review for AL, runtime packages, auto translation, and incremental builds. It also covers Freddy's departure and how the project continues under the engineering systems team.

## Key points

- Create release and increment version number workflows now validate inputs and fail early instead of at the end; more workflows will follow. This is in the latest preview.
- The AL-Go settings schema property gives VS Code suggestions and validates settings, showing a warning on mismatch. It is in preview; 7.2 is mentioned as the release for those not on preview.
- Failing pull requests on new warnings is in preview. It only counts new warnings, can be switched on or off by a setting, does not change CI/CD behavior, and has no configurable threshold.
- BC Container Helper versions earlier than 6.1 no longer work; AL-Go repositories are not affected. Container Helper deprecation is scheduled in about two years, and AL-Go still needs work to become independent of it.
- AL-Go 5.0 still works but versions lower than 5.0 will soon stop working, so run Update AL-Go System Files regularly.
- Direct storage account access for artifact URLs stops at the end of June as part of a Microsoft security push; old blob storage URLs will not work and traffic goes through front door.
- Not supported or not yet effective: data-driven testing in AL-Go, building runtime packages, Copilot code review for AL, auto translation, and page scripting tests on SaaS (blocked by 2FA/MFA, being worked on).

## Chapters

- [0:00](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=0s) Input Validation and Create Release Enhancements
- [1:41](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=101s) AL-Go Settings Schema and Validation
- [3:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=190s) Failing Pull Requests on New Warnings
- [4:07](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s) Announcements: Container Helper and Version Updates
- [5:26](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=326s) Freddy's Departure and Team Transition
- [7:50](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=470s) Team Composition and Pull Request Warning Settings
- [9:09](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=549s) BC Container Helper Deprecation and Future Plans
- [11:08](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=668s) AL-Go Future Investment and Building Artifacts
- [13:08](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s) Page Scripting and Community Events
- [14:56](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=896s) AL-Go Onboarding, Community Engagement, and Artifact Storage
- [17:28](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1048s) Warning Thresholds and Azure DevOps Integration
- [19:55](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1195s) Migration Strategy Between Azure DevOps and GitHub
- [22:27](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1347s) Data-Driven Testing, Copilot Code Review, and Runtime Packages
- [26:11](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1571s) Auto Translation and Incremental Builds Discussion
- [28:23](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1703s) Feature Requests and GitHub Discussions for Backlog
- [31:34](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1894s) GitHub Organization and Enterprise Licensing Structure
- [32:39](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1959s) AL-Go Documentation Gaps and Enterprise Licensing Questions
- [34:02](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2042s) Artifact URL Changes and BC Container Helper Deprecation
- [37:07](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2227s) AL-Go Independence and Security Updates
- [39:18](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2358s) Translation Feature Request and Resource Allocation
- [42:40](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2560s) Commitment to Community and Freddy's Future Plans
- [44:36](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2676s) Management Transition and Team Structure
- [45:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2758s) Closing Remarks and Logistics

## Features

| Feature | Status | At | Evidence |
|---|---|---|---|
| Input Validation for Workflows | preview | [1:00](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=60s) | "So those were the three things we've added to ALGO in the last month. Right now it's in preview." ([4:07](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s)) |
| AL-Go Settings Schema Property | preview | [1:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=118s) | "If you're on preview, you might already see it. Otherwise, you'll have to wait for the 7.2" ([1:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=118s)) |
| Fail Pull Requests on New Warnings | preview | [3:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=190s) | "Right now it's in preview. Uh I don't know if we have any. We'll ship 7.2 soon" ([4:07](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s)) |
| BC Container Helper Deprecation Notice | status not stated | [4:26](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=266s) |  |
| Page Scripting Tests on SaaS Environments | status not stated | [12:55](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=775s) |  |
| Azure DevOps and GitHub Integration | status not stated | [19:14](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1154s) |  |
| Data-Driven Testing Support | status not stated | [22:52](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1372s) |  |
| GitHub Copilot Code Review for AL | status not stated | [24:21](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1461s) |  |
| Building Runtime Packages in AL-Go | status not stated | [25:53](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1553s) |  |
| Auto Translation Feature | status not stated | [26:40](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1600s) |  |
| Incremental Builds Feature | status not stated | [27:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1664s) |  |
| GitHub Discussions Ideas Tab | status not stated | [30:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1844s) |  |
| Artifact URL Migration to Front Door | status not stated | [34:33](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2073s) |  |
| AL-Go Independence from BC Container Helper | status not stated | [36:16](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2176s) |  |

## AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

- other "create release workflow" at [1:12](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=72s)
- other "increment version number workflow" at [1:26](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=86s)
- other "AL-Go file" at [2:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=130s)
- other "AL-Go settings file" at [2:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=130s)
- other "Azure Boards" at [19:39](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1179s)
- other "AI test toolkit" at [23:25](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1405s)
- other "pre-commit" at [25:09](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1509s)
- other "code cut" at [25:19](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1519s)

## Quotes

- [1:00](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=60s) "we've enhanced that in the in the latest preview. Um, so now what we saw was that when you ran the create release workflow,"
- [2:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=130s) "at the top of your ALGO file, you get this schema property. And the schema property will do two things for you. First of"
- [3:37](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=217s) "So, this new feature failing pull requests on your warnings. Um, so it won't change the behavior of your CI/CD workflows. Uh, that'll still"
- [4:26](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=266s) "PC container helper versions earlier than se 6.1 uh, basically don't really work anymore. Um, algo repositories are not affected"
- [5:03](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=303s) "please make sure you regularly update your run update algo system files uh because some of the earlier versions of a go will soon"
- [5:16](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=316s) "5.0 and lower sorry 5.0 will work lower than 5.0 will not work. Uh for reference 5.0 is about a year old now."
- [6:13](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=373s) "I am no longer with Microsoft or I'm still here uh at least for for for some time being. Um but I'm like no"
- [9:09](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=549s) "so busy container upper is not deprecated yet. It's deprecated in about two years time I believe is scheduled. um and and it is"
- [13:08](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s) "We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement of"
- [13:08](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s) "We're not running we are unable to run page scripting tests on SAS environments due to the to the 2FA or MFA requirement"
- [17:49](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1069s) "this feature essentially looks at new warnings only. So if you have a codebase that already has a bunch of warnings and you want"
- [18:06](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1086s) "there are other ways to control breaking and failing on warnings, but not um threshold that is configurable in terms of the number of"
- [19:39](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1179s) "Azure boards integration being one of them. Uh so you can reference work items from GitHub and it creates automatically creates a link"
- [21:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1304s) "If you look at the teams I don't think there's any doubt that GitHub receives the most love and attention from development teams. A"
- [23:42](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1422s) "we haven't built support for that into a go yet. That's something that needs to be investigated and and how we can do that"
- [24:47](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1487s) "guess there is a co pilot uh code review but it's not very good at al yet"
- [26:40](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1600s) "On the ELGO project board, there are some cards about auto translation. Is there any news on that? I don't believe so."
- [27:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1664s) "the biggest feature that came out of that round table was the incremental builds feature"
- [27:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1664s) "the biggest feature that came out of that round table was the incremental builds feature 23 that was in that was that round table"
- [30:44](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1844s) "Seems like it this this is maybe a good opportunity to also promote a little bit the discussions we have on GitHub where we"
- [35:04](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2104s) "those URLs would be something like bc artifacts.blo.s storage.net or something like that. Uh and those will not work in the future."
- [35:43](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2143s) "at the end of June we'll we'll stop you know the ability to access the storage accounts directly and so by that time all"
- [36:33](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2193s) "It is definitely not. we have a still have a bunch of work left to make a go independent of container helper"
- [37:28](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2248s) "the modifications in ALGO will probably I mean you probably won't notice them in a lot of cases things will just happen and suddenly"
- [41:47](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2507s) "we just got another person working on Algo as well, Sebastian. And, uh, yeah, even though Freddy is leaving, we will be continuing to"
- [42:20](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2540s) "there is a statement from uh Dimmitri from Microsoft uh basically also stating that we're not defunding our efforts into the go"
- [43:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2638s) "I'm going to start my own business and figure out how I can I can manage life, work, and whatever experiences I want to"
- [45:14](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2714s) "Elgo will fall under and I mean has fallen under the engineering systems team which is the team I work on Maria work on"
- [45:42](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2742s) "it's been under it's been under our team for a couple of years, but Fred has still been the one coming up with a"
- [47:25](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2845s) "you can always reach us on in the discussion tab on ALGO. There's also a questions uh tab"

## Disclaimers in the video

- [1:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=118s) preview: If you're on preview, you might already see it. Otherwise, you'll have to wait for the 7.2
- [4:07](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=247s) preview: Right now it's in preview. Uh I don't know if we have any. We'll ship 7.2 soon.
- [9:09](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=549s) coming-later: It's deprecated in about two years time I believe is scheduled. um and and it is being replaced by a new module.
- [13:08](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=788s) coming-later: We're unable to run page scripting tests on SAS environments due to the 2FA or MFA requirement but it is being worked on. Whether it's going to be next month or months after that, I don't know. But soon as possible.
- [13:23](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=803s) coming-later: Whether it's going to be next month or months after that, I don't know. But soon as possible.
- [23:42](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1422s) not-in-this-release: we haven't built support for that into a go yet. That's something that needs to be investigated
- [24:47](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1487s) preview: there is a co-pilot uh code review, but it's not very good at AL yet
- [25:58](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1558s) not-in-this-release: never never got to that it's part of the backlog
- [28:23](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1703s) coming-later: sadly not something we've uh had the time to to work on
- [33:10](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=1990s) coming-later: We have empty pages that says coming soon
- [36:33](https://www.youtube.com/watch?v=vDGrVHQHLA0&t=2193s) coming-later: we have a still have a bunch of work left to make a go independent of container helper

Presenters (as heard): Alexander, Maria, Yonas, Freddy, Sebastian, Jonas, Jose Madreal K, Roberto Corella, Ryan, Christian, Dimmitri.