AL-Go version
preview
Describe the issue
Hi,
Our extension has 1 core extension (without dependencies) and 1 extra layer with a dependency on Continia Document Capture.
The Test Next Major workflow ran well until the workflow started Test Next Major started using BC28.
We're using the preview version of the dependencies by nuget url that was provided by Continia:
We added this url in our Test Next Major.settings.json file:
{
"$schema": "https://raw.githubusercontent.com/microsoft/AL-Go/043c3a212d0131d917eb87c9f9d9e8f55bc67179/Actions/.Modules/settings.schema.json",
"artifact": "////nextmajor",
"cacheImageName": "",
"versioningStrategy": 15,
"workflowSchedule": {
"cron": "0 23 * * 0"
},
"workflowConcurrency": [
"group: ${{ github.workflow }}-${{ github.ref }}",
"cancel-in-progress: true"
],
"trustedNuGetFeeds": [
{
"url": "https://pkgs.dev.azure.com/continia-repository/ContiniaBCPrivateFeeds/_packaging/Insider/nuget/v3/index.json",
"authTokenSecret": "CONTINIA_NUGET_TOKEN"
}
]
}
Our tests ran well till Nov 17, 2025.
The only differences I noticed, was the tests are running against BC28 and it can't compile because the extension is not available (although
logs_bc28_fail.zip
it was downloaded and installed).
Expected behavior
Use the preview version of Continia Document Capture during compilation
Steps to reproduce
- Have an extension with dependency on Document Capture (using W1 BC 26 as artifact)
- Run CICD with artifact
W1 BC 26
- Run
Test Next Major and check if it uses BC27
- Update the AL-Go setting to (using W1 BC 27 as artifact)
- Run CICD with new artifact
W1 BC 27
- Run
Test Next Major and check if it uses BC28
logs_bc27_ok.zip
logs_bc28_fail.zip
Additional context (logs, screenshots, etc.)
No response
AL-Go version
preview
Describe the issue
Hi,
Our extension has 1 core extension (without dependencies) and 1 extra layer with a dependency on Continia Document Capture.
The Test Next Major workflow ran well until the workflow started
Test Next Majorstarted using BC28.We're using the preview version of the dependencies by nuget url that was provided by Continia:
We added this url in our
Test Next Major.settings.jsonfile:{ "$schema": "https://raw.githubusercontent.com/microsoft/AL-Go/043c3a212d0131d917eb87c9f9d9e8f55bc67179/Actions/.Modules/settings.schema.json", "artifact": "////nextmajor", "cacheImageName": "", "versioningStrategy": 15, "workflowSchedule": { "cron": "0 23 * * 0" }, "workflowConcurrency": [ "group: ${{ github.workflow }}-${{ github.ref }}", "cancel-in-progress: true" ], "trustedNuGetFeeds": [ { "url": "https://pkgs.dev.azure.com/continia-repository/ContiniaBCPrivateFeeds/_packaging/Insider/nuget/v3/index.json", "authTokenSecret": "CONTINIA_NUGET_TOKEN" } ] }Our tests ran well till Nov 17, 2025.
The only differences I noticed, was the tests are running against BC28 and it can't compile because the extension is not available (although
logs_bc28_fail.zip
it was downloaded and installed).
Expected behavior
Use the preview version of Continia Document Capture during compilation
Steps to reproduce
W1 BC 26Test Next Majorand check if it uses BC27W1 BC 27Test Next Majorand check if it uses BC28logs_bc27_ok.zip
logs_bc28_fail.zip
Additional context (logs, screenshots, etc.)
No response