Supported way for Create Release to include all buildModes artifacts?

[FBakkensen]

I’m using buildModes with conditional settings to build the same app against multiple Business Central major versions.

This works correctly in CI/CD. The build matrix produces artifacts shaped like:

<repo>-<branch>-Apps-1.41.87.0
<repo>-<branch>-TestApps-1.41.87.0
<repo>-<branch>-bc27Apps-1.41.87.0
<repo>-<branch>-bc27TestApps-1.41.87.0
<repo>-<branch>-bc26Apps-1.41.87.0
<repo>-<branch>-bc26TestApps-1.41.87.0
...

The buildModes setup follows the guidance from discussion #2138: one build mode per BC major version, with conditional settings for artifact / applicationDependency.

Minimal reproduction shape:

1. Configure buildModes: default, bc27, bc26.
2. Add conditional settings per build mode for artifact / applicationDependency.
3. Run CI/CD and confirm all build-mode artifacts exist for the same app version.
4. Run Create Release with buildVersion: latest.
5. Observe that the GitHub Release includes only default Apps / TestApps, not the bc27* / bc26* artifacts.

The gap appears when running Create Release with buildVersion: latest.

The GitHub Release only gets the default artifacts:

<repo>-<branch>-Apps-1.41.87.0.zip
<repo>-<branch>-TestApps-1.41.87.0.zip

It does not get the build-mode artifacts:

<repo>-<branch>-bc27Apps-1.41.87.0.zip
<repo>-<branch>-bc27TestApps-1.41.87.0.zip
<repo>-<branch>-bc26Apps-1.41.87.0.zip
<repo>-<branch>-bc26TestApps-1.41.87.0.zip
...

This looks similar to discussion #900, where Create Release ignored a non-default build mode.

From reading v9.0, DetermineProjectsToBuild resolves BuildOrderJson[].buildDimensions from buildModes, and CI/CD uses that as the matrix. But DetermineArtifactsForRelease receives ProjectsJson and searches default artifact names for the selected buildVersion, so it does not appear to mirror the CI/CD build-mode matrix.

What is the supported AL-Go way to make Create Release include all artifacts produced by the buildModes matrix for the selected buildVersion?

Should Create Release include all buildModes artifacts by default? If that would be breaking for existing repositories, would an opt-in setting such as releaseBuildModes or includeBuildModeArtifactsInRelease be the intended design?

Would the intended implementation be to pass build dimensions/build modes into DetermineArtifactsForRelease and include Apps, TestApps, and Dependencies for each resolved build mode?